Dynamic playout buffer for disparate live media output stream

ABSTRACT

A system is provided for dynamic playout buffer for disparate live media output stream. A request is received that comprises a stream identifier and an additional parameter. In accordance with a playout buffer feature and the additional parameter, a first disparate live media output stream is generated based on an insertion of manifest data and indexed metadata of a media segment associated with the stream identifier to a first disparate live media output stream manifest. The playout buffer feature, defined in a first programming schedule, is associated with a corresponding number of media segments representing pre-encoded media assets and/or live input streams referenced in the first programming schedule.

CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE

This patent application is a Continuation application of U.S. patentapplication Ser. No. 17/017,145, filed on Sep. 10, 2020, which claimspriority to, and the benefit of U.S. Provisional Application Ser. No.62/898,582, filed on Sep. 11, 2019, and is a Continuation-in-part ofU.S. Pat. No. 10,965,967, issued on Mar. 30, 2021, which claims priorityto and the benefit from U.S. Provisional Application Ser. No.62/699,131, filed Jul. 17, 2018, and which is a continuation-in-part ofU.S. Pat. No. 11,134,309, issued on Sep. 28, 2021.

This application also makes reference to:

-   U.S. Pat. No. 11,051,061, issued on Jun. 29, 2021;-   U.S. Pat. No. 11,051,074, issued on Jun. 29, 2021;-   U.S. Pat. No. 11,109,086, issued on Aug. 31, 2021;-   U.S. Pat. No. 10,992,973, issued on Apr. 27, 2021;-   U.S. Pat. No. 10,856,016, issued on Dec. 1, 2020;-   U.S. application Ser. No. 17/016,789, filed on Sep. 10, 2020;-   U.S. application Ser. No. 17/017,052, filed on Sep. 10, 2020; and-   U.S. application Ser. No. 17/017,241, filed on Sep. 10, 2020.

Each of the above referenced patent applications is hereby incorporatedherein by reference in its entirety.

FIELD OF TECHNOLOGY

Certain embodiments of the disclosure relate to a television contentpackaging and distribution system. More specifically, certainembodiments of the disclosure relate to a method and system forpublishing a disparate per-client live media output stream based ondynamic insertion of targeted non-programming content and customizedprogramming content, and for providing a dynamic playout buffer fordisparate live media output stream.

BACKGROUND

Recent advancements in the field of television content packaging anddistribution systems have led to a massive development of numeroustechnologies and broadcasting platforms that are revolutionizing the wayconsumer devices access and playout media content. Usually, broadcastingplatforms refer to the types of networks that are used to deliver themedia content to the consumers. Currently, the broadcasting platforms,such as analog terrestrial broadcast, digital terrestrial broadcast,direct-to-home satellite broadcast, cable, Internet Protocol (IP), andover-the-top television (OTT), compete and strive to increase theirappeal by gaining and retaining the audience viewing the media content.

Modern streaming protocols, such as HTTP Live Streaming (HLS) andDynamic Adaptive Streaming over HTTP (DASH), are implemented to supportstreaming of various live content services, such as DIRECTV NOW℠, SLINGTV℠ and PLAYSTAYION™ VUE, to consumer devices. Due to dissemination ofsuch modern streaming protocols in the television, radio, andbroadcasting sector, it is evident that the success of broadcasting willbe dependent on the ability of the network provider to gain access tothe content that consumers demand, and to differentiate their offeringfrom that of incumbent broadcasters or find breakthrough modes of mediacontent delivery. Typically, such modern streaming protocols requirethat a playout buffer for a live media output stream is definite andunchanging, so that a media player at a client device can suitablycreate rules, based on which media segments are fetched, buffered, andplayed out.

Existing systems for Server-Side Ad Insertion (SSAI) support livestreaming and make decisions to insert non-programing content in nearreal-time. However, for On-Demand streaming, such decisions to insertnon-programing content are made upfront. Accordingly, amount of controlthe user can excerpt to influence what non-programming content is shownmay get limited.

Further limitations and disadvantages of conventional and traditionalapproaches will become apparent to one of skill in the art, throughcomparison of such systems with some aspects of the present disclosureas set forth in the remainder of the present application with referenceto the drawings.

BRIEF SUMMARY OF THE DISCLOSURE

Systems and/or methods are provided for publishing a disparateper-client live media output stream based on dynamic insertion oftargeted non-programming content and customized programming content, andfor providing a dynamic playout buffer for disparate live media outputstream, substantially as shown in and/or described in connection with atleast one of the figures, as set forth more completely in the claims.

These and other advantages, aspects and novel features of the presentdisclosure, as well as details of an illustrated embodiment thereof,will be more fully understood from the following description anddrawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

FIG. 1A is a block diagram that illustrates an exemplary system forpublishing a disparate per-client live media output stream based ondynamic insertion of targeted non-programming content and customizedprogramming content, and for providing a dynamic playout buffer for adisparate live media output stream, in accordance with exemplaryembodiments of the disclosure.

FIG. 1B is a block diagram that illustrates an exemplary dynamicad/content insertion system (DACIS) for publishing a disparateper-client live media output stream based on dynamic insertion oftargeted non-programming content and customized programming content, andfor providing a dynamic playout buffer for a disparate live media outputstream, in accordance with exemplary embodiments of the disclosure.

FIG. 2 illustrates segmentation of live input streams and pre-encodedmedia assets for a first programming schedule for publishing a disparateper-client live media output stream based on dynamic insertion oftargeted non-programming content and customized programming content bythe DACIS of FIG. 1B, and for providing a dynamic playout buffer for adisparate live media output stream, in accordance with exemplaryembodiments of the disclosure.

FIG. 3 illustrates an exemplary scenario associated with publishing adisparate live media output stream by the DACIS of FIG. 1B, inaccordance with an exemplary embodiment of the disclosure.

FIGS. 4A to 4D collectively depict a flowchart illustrating exemplaryoperations for publishing a disparate per-client live media outputstream based on dynamic insertion of targeted non-programming contentand customized programming content by the DACIS of FIG. 1B, inaccordance with an exemplary embodiment of the disclosure.

FIG. 5 is a conceptual diagram illustrating an example of a hardwareimplementation for the DACIS employing a processing system forpublishing a disparate per-client live media output stream based ondynamic insertion of targeted non-programming content and customizedprogramming content, and for providing a dynamic playout buffer for adisparate live media output stream, in accordance with exemplaryembodiments of the disclosure.

FIGS. 6A and 6B collectively depict a flowchart illustrating exemplaryoperations for providing a dynamic playout buffer for a disparate livemedia output stream by the DACIS of FIG. 1B, in accordance with anexemplary embodiment of the disclosure.

DETAILED DESCRIPTION OF THE DISCLOSURE

Certain embodiments of the disclosure may be found in a method andsystem for publishing a disparate per-client live media output streambased on dynamic insertion of targeted non-programming content andcustomized programming content, and for providing a dynamic playoutbuffer for a disparate live media output stream. Various embodiments ofthe disclosure provide a method and system that not only provide livechannel offerings in a cost-effective manner but also provide enhanced,intelligent, and personalized viewer experience to increase their appealby retaining the audience viewing the media content.

Modern streaming protocols, such as HLS and DASH, break media contentinto numerous small media content segments, typically less than 10seconds in length. Further, the modern streaming protocols implementmanifests that instruct a media player on what media content segment toretrieve and play next. The manifest may enlist the media segments thatmake up the full length of the media asset. The manifest may includeinformation, based on which the media player at a consumer device may beable to determine the media segments. The manifest and/or media contentsegment may also include and/or specify additional information tofacilitate a media player to transition smoothly between media contentstreams from different sources. The manifest may be used for creating aplaylist of multiple media content files, or for interrupting mediacontent with advertising and then resuming the media content.

Such modern streaming protocols support video-on-demand (VOD) assets andlive content as well. The VOD assets prepared for distribution, forexample Internet distribution, may have a sequence of short durationsegments added to a manifest. The short duration segments may beseparate physical files or pointers (real or to be calculated) to theshort media content segments inside a larger file. On the other hand, incase of live content, new short content media segments are madeavailable as soon as they are created. In some protocols, each newsegment is added to a manifest while in others the media player isprovided with information that may be utilized to calculate what thenext live segment will be. In the latter case, a signal in the mediacontent itself may be utilized to inform the player when to re-inspector check the manifest for a change in media content. In live streaming,delivery of live content is supported by making available each new shortmedia content segments as soon as such media content segments aregenerated. In some protocols, new media content segments may be added tothe manifest, while in others, the media player calculates necessaryinformation about the next live media content segments.

Further, in live streaming, a manifest is published that represents anindex of media segments to be played/consumed by a client device. As alive stream has no definable end, it may not be possible for such indexto point to all past and future media segments. As media segments arepublished and/or played, the oldest media segment is removed, a newmedia segment appended to the index, and thus, a moving playout bufferor a live window of the media segments is created. Typically, suchmodern streaming protocols require that the playout buffer for a livemedia output stream is definite and unchanging, so that a media playerat a client device can suitably create rules, based on which mediasegments are fetched, buffered, and played out.

In accordance with various embodiments of the disclosure, a system isprovided for publishing a disparate per-client live media output streambased on dynamic insertion of targeted non-programming content andcustomized programming content. One or more processors in the system maybe configured to receive a first manifest request from a first clientdevice, wherein the first manifest request comprises one or moreparameters. The one or more processors in the system may be furtherconfigured to determine a first additional content that comprises acustomized first programming content and a targeted firstnon-programming content for the first client device based on the one ormore parameters and the associated indexed metadata. The one or moreprocessors in the system may be further configured to generate a firstprogramming schedule for the first client device based on the selectedone or more live input streams and/or the one or more pre-encoded mediaassets, the associated indexed metadata, and the determined firstadditional content. Accordingly, one or more live input stream manifestsand/or one or more pre-encoded media asset manifests published in acontent delivery network and associated indexed metadata may be selectedbased on the one or more parameters. The one or more processors in thesystem may be further configured to publish a first disparate live mediaoutput stream manifest for the first client device based on insertion ofthe selected one or more live input stream manifests and/or the one ormore pre-encoded media asset manifests, the associated indexed metadata,and the determined first additional content in accordance with the firstprogramming schedule generated for the first client device.

In accordance with another aspect of the disclosure, a system isprovided for publishing a first programming schedule that may referenceat least one or more pre-encoded media assets and/or one or more liveinput streams. The first programming schedule may comprise one or moreplayout buffer features enabled via one or more constraints and rights.Each playout buffer feature of the one or more playout buffer featuresmay be associated with a corresponding number of media segments that mayrepresent the one or more pre-encoded media assets and/or one or morelive input streams. A request may be received that comprises at least astream identifier and at least an additional parameter. In accordancewith a playout buffer feature from the one or more playout bufferfeatures and at least the additional parameter, manifest data andindexed metadata of one or more media segments associated with thestream identifier may be inserted to a first disparate live media outputstream manifest. Accordingly, a first disparate live media output streammay be generated.

FIG. 1A is a block diagram that illustrates an exemplary system forpublishing a disparate per-client live media output stream based ondynamic insertion of targeted non-programming content and customizedprogramming content, and for providing a dynamic playout buffer fordisparate live media output stream, in accordance with exemplaryembodiments of the disclosure. Referring to FIG. 1A, the system 100,comprises a media packaging and distribution system 102 that iscommunicatively coupled to published data sources 104 a, . . . , 104 n,Ad decisioning servers 106 a, . . . , 106 n, via a network 108 and/orother programmatic means. There are shown consumer devices 110 a, . . ., 110 n that are communicatively coupled to the network 108. The mediapackaging and distribution system 102 may comprise at least a DACIS 103,a Content Decisioning Service (CDS) 105, a Content Packaging andDistribution System (CPDS) 107, a stream selection service 142, and arepository of schedules, rights, and user preferences database 144.There are also shown source devices 118 communicatively coupled to themedia packaging and distribution system 102 through the network 108. Anexternal data source 120 is also provided, which is communicativelycoupled to the media packaging and distribution system 102 through thenetwork 108.

The media packaging and distribution system 102 may comprise suitablelogic, circuitry, and interfaces that may be configured to execute codethat handles media content comprising audio, video, images, metadata,manifests, and/or other data (embedded and/or externally referenced).The media content may include a video, an audio, a combination of audioand video presentations, and/or embedded or externally referencedmetadata, a combination of multiple-audio, multiple-video, and/orembedded or externally referenced metadata. Accordingly, the mediapackaging and distribution system 102 publishes a disparate per-clientlive media output stream based on dynamic insertion of targetednon-programming content and customized programming content.

In this regard, the media packaging and distribution system 102 mayprovide video programming services to viewers, usually for asubscription fee (such as pay television). The media packaging anddistribution system 102 also handles distribution, for example,multicasting, unicasting, broadcasting, streaming, for one or morechannels to be viewed on one or more of the plurality of consumerdevices 110 a, . . . , 110 n.

The media packaging and distribution system 102 may be operated by anentity related to handling or distribution of media content, forexample, a broadcast provider or operator, or a network provider ornetwork operator. The entity related to handling or distribution ofmedia content may also be referred to as a content owner, a distributor,a syndicator, a re-distributor, a content aggregator, a search,discovery, or cataloging service provider, or any other entity activelyor passively involved with the distribution, cataloging, or referencingof complete or partial presentations of media content. Throughout thisdocument, the terms broadcast provider or broadcast operator, andnetwork provider or network operator may be utilized to refer to theentity related to handling or distribution of media content,interchangeably. The broadcast provider may handle a single channel or aplurality of channels, or one or more networks. The broadcast providermay be configured to distribute content via one or more platforms, forexample, traditional over-the-air broadcast channels, radio, cabletelevision networks, satellite communication networks, the Internet,and/or other content delivery networks (CDNs). In this regard, thebroadcast provider may be configured to execute code that communicateslinear video feeds (also referred to as a network television feed orbroadcast feed) to the media packaging and distribution system 102. In abroadcast chain, the broadcast provider may receive actual content, forexample, from a production studio, in one or more source formats.Examples of the one or more source formats may include, but are notlimited to a tape file, or a live feed that may be further converted toa serial digital interface (SDI) video interface and/or on ahigh-definition SDI (HD-SDI) video interface for processing and playout.The broadcast provider may further process the content, such asinsertion of graphics, closed captions, preparation of programmingschedule, insertion of triggers, and the like, and provide finaldelivery by a broadcasting apparatus. The communicated linear video feedand the playout schedule may correspond to a channel, such as CNNchannel that is broadcast to the media packaging and distribution system102, via a communication network. The linear video feed may bebroadcasted as a multi-program transport stream (MPTS) (also referred toas a live video feed) to the media packaging and distribution system102, via the network 108. The broadcast provider may be owned by (orassociated to) a broadcast provider or operator, a network provider oroperator, or a content provider or operator.

The media packaging and distribution system 102 may receive the MPTS,which includes the signaling content and metadata, from the broadcastprovider based on, for example, current society of cabletelecommunication engineers (SCTE) standards (SCTE-35 and SCTE-224) tocontrol web and regional blackouts, network end of day switching, andadvertisement insertion. For example, the media packaging anddistribution system 102 may be signaled for various blackout types within-band SCTE-35 message. Further, the media packaging and distributionsystem 102 may receive program metadata that specifies certain events oroperations, such as, for example, when to blackout shows. Examples oflegacy distribution system that may be benefitted from the mediapackaging and distribution system 102 may include direct-broadcastsatellite (DBS) providers, cable television (CATV) systems, and otherwireline video providers and competitive local exchange carriers (CLECs)using, for example, IPTV.

The DACIS 103 may comprise suitable logic, circuitry, and interfacesthat may be configured to leverage one-to-one scale of traditional SSAIsystems to support custom programming content choices and not justtargeted non-programming content. For example when the user selects tojoin a live stream, a content decisioning system, such as the CDS 105could determine that, instead of joining the live stream for the lastfew minutes of a program prior to the start of the intended program, theuser should instead be shown content more relevant to the user so as toprevent them from tuning away, e.g. show a personalized set ofbasketball highlights and ads to a user who likely joined the stream towatch a basketball game that is coming on next. The DACIS 103 replacesoriginal content in the live stream prior to game start with userrelevant content, such that upon its conclusion, the user is seamlesslypresented the game.

The DACIS 103 may be further configured to, via a programming scheduleor tag indicator in a disparate live media output stream manifest, benotified of one or more content graphical treatment opportunities withinthe media content. The DACIS 103 may be further configured to makerequired non-programing content calls on behalf of the plurality ofconsumer devices 110 a, . . . , 110 n. Accordingly, the DACIS 103 mayprovide the plurality of consumer devices 110 a, . . . , 110 n withinformation needed to execute the graphical treatment graphical contentvia a secure out-of-band channel between the DACIS 103 and the pluralityof consumer devices 110 a, . . . , 110 n. In accordance with anembodiment, the DACIS 103 may be configured to include not showingnon-programming content that a user of a consumer device may elected toskip or rated poorly in an earlier non-programming content break.Further, the DACIS 103 may enable the user to skip non-programmingcontent as the user interacted with a previous non-programming contentor made a purchase and the advertiser elected to sponsor the remainderof the programming content.

In accordance with an embodiment, the DACIS 103 may be configured toprovide seamless failover between redundant disparate live media outputstreams for large events, thus improving reliability. In certaininstances, some of the plurality of consumer devices 110 a, . . . , 110n may support a primary and backup disparate live media output streamsand are able to fail between them. In other instances, others of theplurality of consumer devices 110 a, . . . , 110 n may not support theprimary and backup disparate live media output streams. In suchinstances, the consumer devices may attempt to join an alternativedisparate live media output stream after occurrence of an event such asa device failure or crash. For such consumer devices, the DACIS 103 maybe configured to monitor both the primary and backup disparate livemedia output streams, and if there is a failure, write the alternativedisparate live media output stream into the disparate live media outputstream manifest.

Each of the plurality of published data sources 104 a, . . . , 104 n maybe coupled to one or more television networks and may comprise suitablelogic, circuitry, and interfaces that may be configured to execute codethat provides actual audiences for programs that were distributed. Asillustrated in FIG. 1A, the plurality of published data sources 104 a, .. . , 104 n are coupled to the media packaging and distribution system102 via the network 108 and configured to monitor audience drift to oraway from a tuned channel airing a live media output stream. Theplurality of published data sources 104 a, . . . , 104 n may provideactual audiences for programs to the indexing and storage system 116. Anexemplary published data source may be Nielsen. Nielsen has thecapability to determine when a viewer watches the same set of mediaitems, for example, advertisements and/or promotional content, inprogramming data, such as an episode, in a live video feed within 3 daysof original airing, and provide Nielsen “C3” credit. Another exemplarypublished data source may be a published database that provides ratingsfor a media item, such as gross rating point (GRP). The GRP isadvertising or promotion impact measure for each advertising and/orpromotional campaigns, known in the art. Other exemplary published datasources may also include direct/indirect access to other public orprivate data sources (persistent or ephemeral) through programmaticmeans.

The CDS 105 may comprise suitable logic, circuitry, and interfaces thatmay be configured to determine, upon request, which programming content(or partial programming content) to deliver back to the plurality ofconsumer devices 110 a, . . . , 110 n. Thus, the CDS 105 may beconfigured to insert additional content (including non-programmingcontent) or replace existing content, according to one or moreparameters provided by the plurality of consumer devices 110 a, . . . ,110 n and data stored in various external systems and/or databases.

The Ad decisioning servers 106 a, . . . , 106 n may comprise suitablelogic, circuitry, and interfaces that may be configured to implement atleast an advertisement decisioning component that may be used during areal-time content or advertisement placement activity, for exampleduring dynamic ad insertion. The Ad decisioning servers 106 a, . . . ,106 n may further determine ad-load opportunity, based on targeting datafrom schedules, rights, and user preferences database.

For example, commercial or non-commercial advertisements may bedynamically inserted within program segments of the live input streamsbased on the detected upcoming indicator, such as an inbound trigger, asignaling point, and/or a signal in a pre-encoded media asset and/or alive input stream by the Ad decisioning servers 106 a, . . . , 106 n.

In an embodiment, the DACIS 103 may be generalized as a proxy betweenthe plurality of consumer devices 110 a, . . . , 110 n and the Addecisioning servers 106 a, . . . , 106 n. In one implementation, arequest is sent from a consumer device to the DACIS 103. The DACIS 10may call on of the Ad decisioning servers 106 a, . . . , 106 n todetermine a set of non-programming content that may be inserted into thedisparate live media output stream.

The CPDS 107 may comprise suitable logic, circuitry, and interfaces thatmay be configured to index programming content, which is prepared forusage by a system, such as the stream publishing engine 114. The CPDS107 may further define metadata detailing various facets of theprogramming and/or non-programing content including duration, knownlocations and opportunities for programing and/or non-programing contentinsertion/replacement.

The network 108 may be any kind of network, or a combination of variousnetworks, and it is shown illustrating exemplary communication that mayoccur between the Ad decisioning servers 106 a, . . . , 106 n and themedia packaging and distribution system 102. For example, the network108 may comprise one or more of a cable television network, theInternet, a satellite communication network, a wide area network (WAN),a medium area network (MAN), and a local area network (LAN). Although anetwork 108 is shown, the disclosure is not limited in this regard;accordingly, other exemplary modes may comprise uni-directional orbi-directional distribution, such as packet-radio, satellite.Furthermore, the network 108 is an exemplary embodiment of adistribution system.

The consumer devices 110 a, . . . , 110 n may refer to end-user devicesor consumption devices where the content is played to be consumed by auser. The number of impressions of a media item, such as anadvertisement and/or promotional media, on such plurality of consumerdevices 110 a, . . . , 110 n determines the advertising impact orpromotion impact and number of actual audiences achieved duringcampaigns. Examples of the consumer devices 110 a, . . . , 110 n mayinclude, but are not limited to, connected TVs, connected TV with pairedand/or connected devices (e.g., HDMI sticks, tablets), personalcomputer, smartphone, tablet, OTT set-top, or hybrid set-top, and secondscreen devices such as smartphones, tablets, game consoles, personalcomputers, set-top boxes, and embedded devices. The consumer devices 110a, . . . , 110 n may further include process/system that may process theoutput for any means, regardless of the capability or intent to decodefor media presentation, and on which the consumer may launch a web page,a web application, or a web service to view media content.

The source devices 118 may comprise suitable logic, circuitry, andinterfaces that may be configured to communicate a live media feed orlive input streams of a channel, such as an existing channel, to themedia packaging and distribution system 102. In accordance with anembodiment, the live input streams of the channel may correspond to abroadcast feed. The source device 118 may be communicatively coupled tothe network 108.

The external data source 120 may comprise suitable logic, circuitry, andinterfaces that may be configured to execute code that handles retrievaland storage of audience data that corresponds to subscribers of theplurality of consumer devices 110 a, . . . , 110 n. The audience datamay include demographics data, audience targeting data, trending data,device type data, device platform data, and content recognition-baseddata, such as automatic content recognition (ACR)-based data. Thetrending data may comprise information on what's trending in the socialnetworks (or platforms), such as Twitter®, Facebook®, and the like. Thetrending data also comprises information on what's trending based onsocial engagement, such as number of likes or votes to a particularmedia item, or number of people watching a particular media item. Thetrending data may indicate an aggregate interest level of a number ofusers in the social networks for a particular media item. For example, athousand or more shares, or likes by a number of users may indicate ahighly popular media item.

The stream selection service 142 may comprise suitable logic, circuitry,and interfaces that may be configured to execute code that may beconfigured to provide a consumer device, for example, the consumerdevice 110 a, requesting to view the disparate live media output streamwith a correct variant of disparate live media output stream, based onthe geolocation and identification of the consumer device 110 a, alongwith data retrieved from the repository of schedules, rights, and userpreferences database 144.

The repository of schedules, rights, and user preferences database 144may comprise suitable logic, circuitry, and interfaces that may beconfigured to store the schedules for all source feeds, availabilityrights for all the content in the schedules, regional blackout zones forthe various sports leagues, predefined location-based viewingpreferences, individual client viewing preferences, and any viewing ortransition rules provided by the stream owner operator.

In operation, in accordance with an aspect of the disclosure, uponreceiving a first manifest request from a consumer device, the DACIS 103may be configured to publish a manifest of a first disparate live mediaoutput stream for the consumer device. The first disparate live mediaoutput stream may be chosen by the DACIS 103, at the time of the firstmanifest request, to best target a consumer device, according to aplurality of client-specific parameters. The plurality ofclient-specific parameters may comprise user preferences andidentifiers, consumer device preferences and identifiers, and one ormore rules/rights governed by geolocation data and current position ofplayback of a first disparate live media output stream at the consumerdevice. The first disparate live media output stream manifest may begenerated, at the time of the first manifest request, to includeadditional content, such as the targeted non-programing content and thecustomized programming content. Examples of the targeted non-programingcontent may include, but are not limited to, advertisements,personalized (per-user) advertisements, video advertisements, andgraphical treatment (such as overlays). The targeted non-programingcontent may further include first interactive elements, such as anoption to purchase goods or content, and second interactive elements.The second interactive elements may further affect the generation of thefirst disparate live media output stream manifest by providing variousoptions. For example, a first option may be to skip a given ad, a secondoption may be to skip future ads for remainder of the playback of thefirst disparate live media output stream, a third option may be tochoose one or more ads of a given category, or a fourth option may betoo watch all ads immediately to avoid ads for the remainder of theplayback. Examples of the customized programing content may include, butare not limited to, promotional content, short-form content, oralternate content (content replacing that of the requested firstdisparate live media output stream.

The DACIS 103 may further receive metadata associated with the contentand additional content for the first disparate live media output streamfrom the CPDS 107. The metadata may include, for example, ad breaklocations, graphical treatment marker/triggers, SCTE35 markers, contentduration, personalized content opportunities, and one or more decisionpoint locations.

In accordance with an embodiment, the DACIS 103 may be configured toconvert a pre-encoded media asset to the first disparate live mediaoutput stream to facilitate one or more subsequent modifications on thefirst disparate live media output stream. The one or more subsequentmodifications may correspond to a user selection, a user preference, achange in a first programming schedule, or a time or geolocation-basedrule. In accordance with an embodiment, the DACIS 103 may be configuredto perform another conversion of remainder of the first disparate livemedia output stream into the one or more pre-encoded media assets tofacilitate download of the one or more pre-encoded media assets at theconsumer device and mitigate dependency on the DACIS 103 for playback ofremaining portion.

In accordance with another aspect of the disclosure, upon receiving thefirst manifest request, a manifest of the first disparate live mediaoutput stream may be altered to include additional or alternate content,apart from the content originally scheduled for playback. The DACIS 103may be configured to determine which content to include/replace byutilizing one or more parameters. The one or more parameters mayinclude, but not limited to, URL requested for playback, and anidentifier referencing a record for an existing first disparate livemedia output stream or an external connected system, such as the CPDS107. The one or more parameters may include a plurality ofclient-specific parameters that may comprise user preferences andidentifiers, consumer device preferences and identifiers, and one ormore rules/rights governed by geolocation data and current position ofplayback of a first disparate live media output stream at the consumerdevice. The one or more parameters may include a plurality ofclient-specified attributes derived from user interaction with theconsumer device. The plurality of client-specified attributes mayinclude, for example, a preference for a given type and/or category (orcategories) of programming content, a possible time constraint orduration to fill with content. The time constraint or duration to fillwith content may be determined by user preferences from an externalsystem, such as the repository of schedules, rights, and userpreferences database 144, a range defined in the first client manifestrequest, schedule tolerances, as defined in the repository of schedules,rights, and user preferences database 144, devicepreferences/identifiers declared in the first manifest request, and aprior consumer request, or found in the repository of schedules, rights,and user preferences database 144. The time constraint or duration tofill with content may be further determined by geolocation informationdeclared in the first manifest request or found in the first manifestrequest, or external database, such as the repository of schedules,rights, and user preferences database 144, or external systems, such asa content recommendation engine. The one or more parameters may furtherinclude rules, rights, and schedule data stored in the DACIS 103 or anadjacent, external system—such as the repository of schedules, rights,and user preferences database 144.

In accordance with an embodiment, the DACIS 103 may determine where toplace new or alternate content within the requested disparate live mediaoutput stream. The DACIS 103 may utilize metadata, such as ad breaklocations, graphical treatment markers/triggers, SCTE35 markers, contentduration, and one or more decision point locations. The metadata may besourced from a system that has indexed metadata for the asset, such asthe CPDS 107. The DACIS 103 may generate a new schedule from thedetermined alterations in the first disparate live media output stream.The DACIS 103 may transmit resulting schedule to the stream publishingengine 114 to generate a final disparate live media output stream. Thefinal disparate live media output stream may be delivered back tooriginating client. The stream publishing engine 114 may generate thefirst disparate live media output stream manifest based on one of apre-defined conversion modes. The pre-defined conversion modes maycorrespond to pre-encoded media assets to live stream mode, pre-encodedmedia assets to live stream mode with scalable architecture, a livestream to live stream mode, and a mixed mode corresponding to switchingbetween pre-encoded media assets and live streams.

The final disparate live media output stream may contain one or moredecision points, which, if configured, may be presented by the consumerdevice to the user. In this regard, the final disparate live mediaoutput stream may be delivered as a live stream between the decisionpoints whether or not the programming content selected by a user ispre-encoded media asset or a live input stream. At the one or moredecision points, the user interaction may correspond to one of a desiredselection corresponding to the user interaction with one or moreinteractive elements, or a default selection corresponding tonon-interaction of a user with the customized first programming contentand/or the targeted first non-programming content in the first disparatelive media output stream played back by the media player. The desiredselection or the default selection may be transmitted to an externalstorage system that is the repository of schedules, rights, and userpreferences database 144.

In accordance with an embodiment, at the one or more decision points,the one or more interactive elements may facilitate exclusion of thetargeted first non-programming content or the customized firstprogramming content and replacement by default content. The one or moreinteractive elements may further facilitate selection of alternatecustomized first programming content, selection of a subsequent secondprogramming content, approval or disapproval of the selected customizedfirst programming content, and/or exclusion of subsequent secondnon-programming content for a remaining portion of the first disparatelive media output stream played back by the media player. The one ormore interactive elements may further facilitate selection of one ormore targeted first non-programming content of a specific category, orviewing of some or all of the targeted first non-programming contentimmediately to avoid some or all of the targeted first non-programmingcontent for the remaining portion of the first disparate live mediaoutput stream played back by the media player.

In accordance with another aspect of the disclosure, the DACIS 103, uponthe first manifest request, may seamlessly transition the firstadditional content to an alternate additional content according todetermination made by the stream selection service 142, based on one ormore transition parameters. The one or more transition parameters maycomprise one or more parameters from the first manifest request, currentstate of the first disparate live media output stream manifestdetermined based on accessibility, regular update, and suitableencoding, digital rights management, and compatibility with the firstclient device, rules provided by a stream owner operator, and userpreferences defined in the repository of schedules, rights, and userpreferences database 144.

The DACIS 103 may retrieve alternate metadata for the alternateadditional content from the CPDS 107. The alternate metadata mayindicate a location to seamlessly transition from the first additionalcontent to the alternate additional content, and may include ad breaklocations, graphical treatment markers/triggers, SCTE35markers/triggers, content duration, and/or one or more decision points.The DACIS 103 may be configured to determine placement of the alternateadditional content within the first disparate live media output streammanifest based on the associated indexed metadata and the alternatemetadata. The DACIS 103 may generate an alternate programming schedulefor the first client device based on the alternate additional contentand the alternate metadata. The DACIS 103 may transmit the generatedalternate programming schedule to the stream publishing engine 114. Thestream publishing engine 114 may generate a final disparate live outputstream manifest for the consumer device.

In accordance with an embodiment, the DACIS 103 may revoke the firstdisparate live media output stream manifest published for the firstconsumer device based on an identifier primitive associated with thefirst disparate live media output stream of the first consumer device inan instance in which a media player of the first consumer device isdetermined to be a plagiarized media player with unauthorized access tocontent. In such embodiment, the first disparate live media outputstream may include at least one unique identifier inserted by the DACIS103.

In accordance with another aspect of the disclosure, the DACIS 103 maybe configured to provide a dynamic playout buffer for disparate livemedia output stream to be viewed on a plurality of consumer devices(such as the consumer devices 110 a, . . . , 110 n). The DACIS 103, maybe configured to publish the first programming schedule 111 that mayreference at least one or more pre-encoded media assets and/or one ormore live input streams. The published first programming schedule maycomprise one or more playout buffer features enabled via one or moreconstraints and rights. Each playout buffer feature of the one or moreplayout buffer features may be associated with a corresponding number ofmedia segments that represents the one or more pre-encoded media assetsand/or the one or more live input streams. The DACIS 103 may be furtherconfigured to receive a request that comprises at least a streamidentifier and at least an additional parameter. The DACIS 103 may befurther configured to insert manifest data and indexed metadata of oneor more media segments associated with the stream identifier to a firstdisparate live media output stream manifest in accordance with a playoutbuffer feature from the one or more playout buffer features and at leastthe additional parameter. The DACIS 103 may be further configured togenerate a first disparate live media output stream based on theinsertion of the manifest data and indexed metadata to the firstdisparate live media output stream manifest.

FIG. 1B is a block diagram that illustrates an exemplary DACIS forpublishing an updated disparate live media output stream in mixed modebased on user selection, and for providing a dynamic playout buffer fordisparate live media output stream, in accordance with exemplaryembodiments of the disclosure. Referring to FIG. 1B, the DACIS 103comprises a first programming schedule 111, an alternate programmingschedule 113, a stream publishing engine 114, a personalized experiencemanager (PEM) 115, and an indexing and storage system 116. FIG. 1Bfurther illustrates a content delivery system 130, which is an exampleof the network 108, client devices 132 a, . . . , 132 n, whichcorrespond to the plurality of consumer devices 110 a, . . . , 110 n.There is further shown a per-client disparate live media output stream117 a, . . . , 117 n for corresponding client device from the clientdevices 132 a, . . . , 132 n.

In some embodiments of the disclosure, the stream publishing engine 114,the PEM 115, and the indexing and storage system 116 may be integratedto form an integrated system, as illustrated in FIG. 1B. In someembodiments of the disclosure, as shown, the stream publishing engine114, the PEM 115, and the indexing and storage system 116 may bedistinct. In this regard, the PEM 115 may be implemented external to theDACIS 103 without loss of generality. Other separation and/orcombination of the various entities of the exemplary media packaging anddistribution system 102 illustrated in FIG. 1B may be done withoutdeparting from the spirit and scope of the various embodiments of thedisclosure. In an embodiment, the implementation of the DACIS 103 may beon the server-side. In another embodiment, the implementation of theDACIS 103 may be on the client-side.

The first programming schedule 111 may correspond to an instruction setfor a disparate live media output stream for a corresponding clientdevice. The first programming schedule 111 may inform the streampublishing engine 114 about pre-encoded media assets and live inputstreams as well as when and how to switch between the variouspre-encoded media assets and live input streams. The first programmingschedule 111 may also support defining break durations for mid roll ads,break locations, and durations in the pre-encoded media asset and liveinput stream switches.

The alternate programming schedule 113 may correspond to an instructionset for an updated or alternate disparate live media output stream. Thealternate programming schedule 113 may inform the stream publishingengine 114 about the alternate pre-encoded media asset and/or thealternate live input stream, and alternate additional content.Specifically, the alternate programming schedule 113 may indicate thatwhen and how to switch between the various disparate live media outputstreams.

The stream publishing engine 114 in the DACIS 103 may be configured togenerate disparate live media output stream manifests and variants ofdisparate live media output stream manifests. The stream publishingengine 114 may be configured to publish unique-to-client streamingmanifests leveraging different indexes created by the indexing andstorage system 116 from the various live input streams, pre-encodedmedia assets, targeted non-programming content and customizedprogramming content based on a defined per-client schedule.

The PEM 115 in the DACIS 103 may be configured to personalize viewerexperience of users by communicating with existing content decisioningsystems, such as CDS 105, and executing/converting schedules provided,for example from the first programming schedule 111 to the alternateprogramming schedule 113. The PEM 115 in the DACIS 103 may be furtherconfigured to communicate with an ad server, such as the Ad decisioningserver 106 a, and stitching in targeted first non-programming contentand customized first programming content, as required by the firstprogramming schedule 111 and user preferences. The PEM 115 in the DACIS103 may be further configured to generate a schedule for a disparatelive media output stream of personalized content (i.e., clips ormovies), communicating with the stream selection service 142 to switchor failover to different disparate live media input streams, and controloverlays and other events triggered via the disparate live media outputstream. In accordance with an embodiment, the stream selection service142 may be used to switch between different output streams when a clientdevice is requesting directly from the stream selection service 142. Inaccordance with other embodiment, the stream selection service 142 maybe used to switch between different streams that may act as inputs forthe PEM 115 and/or stream publishing engine 114 to generate a new outputstream.

The indexing and storage system 116 in the DACIS 103 may be configuredto ingest pre-encoded media assets, advertisement, and (continuously)live stream source manifests, indexes the media content segments,indexes one or more program indicators (such as program boundaries),non-programming indicators (such as ad break locations, overlayopportunities credits, and DRM systems supported, in the repository ofschedules, rights, and user preferences database 144.

The per-client disparate live media output streams 117 a, . . . , 117 nmay correspond to disparate live media output stream comprising liveinput streams and/or pre-encoded media assets to be sent back to aclient device, upon request, that has been generated from a per-clientschedule, such as the first programming schedule 111. Various mediacontainer formats of the live input streams and/or pre-encoded mediaassets may include, but are not limited to, transport stream (TS),fragmented MP4 (fMP4), Common Media Application Format (CMAF) and thelike.

The content delivery system 130 may correspond to the network 108,described in FIG. 1. The content delivery system 130 may comprisenetworks configured for distributing media content to the plurality ofclient devices 132 a, . . . , 132 n. Generally, the term “content,”“metadata,” “media,” and similar words are used interchangeably to referto any type of media—audio, videos, datacasts, music, text, images,graphics, articles, still photos, animated photos, moving photos, photogalleries, video galleries, infographics, maps, polls, guestbiographies, tweets or other social media, blog posts, and/or the like.The content delivery system 130 may be configured to provide a pluralityof disparate live media output streams to the plurality of clientdevices 132 a, . . . , 132 n (in case packaged content is available onthe network 108) or from the content packaging and distribution system107 (in case packaged content is not available on the network 108). Theplurality of disparate live media output streams may be provided to theplurality of client devices 132 a, . . . , 132 n via, for example, atransport stream, a segmented streaming, a progressive download, or anyother modes of distributing a multimedia presentation, such as via anover-the-air content delivery/distribution network, a linear contentdelivery/distribution network, a cable content delivery/distributionnetwork, a satellite content delivery/distribution network, an InternetProtocol (IP) based content delivery/distribution network, and/or thelike.

The client devices 132 a, . . . , 132 n may correspond to consumerdevices 110 a, . . . , 110 n. In accordance with an embodiment, theclient devices 132 a, . . . , 132 n may be content recognition(CR)-enabled devices, such as automatic content recognition enableddevices. The client devices 132 a, . . . , 132 n may be configured tocommunicate with the Ad decisioning server 106 a, via the contentdelivery system 130, or a separate communication network.

The stream selection service 142 may comprise suitable logic, circuitry,and interfaces that may be configured to provide a client device, forexample, the client device 132 a, requesting to view a disparate livemedia output stream with a correct variant of disparate live mediaoutput stream, based on the geolocation and identification of the clientdevice 132 a, along with data retrieved from the repository ofschedules, rights, and user preferences database 144. The streamselection service 142 may further receive user preferences of a userassociated with the client device 132 a, for example, to view therecommended/desired existing disparate live media output stream on theclient device 132 a. The stream selection service 142 may further storethe received preferences in the repository of schedules, rights, anduser preferences database 144, and also communicate with the PEM 115.The stream selection service 142 acts as an interface between the PEM115 of the media packaging and distribution system 102 and the pluralityof client devices 132 a, . . . , 132 n.

The repository of schedules, rights, and user preferences database 144may comprise suitable logic, circuitry, and interfaces that may beconfigured to execute code to store content rights, user preferences,regional preferences, live schedules, and regional rights. For example,content rights may store availability and platform rights for live inputstreams in the first programming schedules, such as the firstprogramming schedule 111, the user preferences may store preferences ofindividual user viewing preferences, the regional preferences may storeregional viewing preferences, the live schedules may store the schedulesfor live input streams, and the regional rights may store regionalblackout zones for the various sports leagues, for example. Therepository of schedules, rights, and user preferences database 144 mayfurther store data supplied from a stream owner/operator includingrequirements, preferences, such as pre-defined location-based viewingpreferences, stream transition rules, and any required client data, suchas service level and zip code.

In operation, in accordance with an aspect (regarding just-in-timeinsertion of non-programming content and/or programming content) of thedisclosure, a media player in a consumer device, such as the consumerdevice 110 a, may send a first manifest request to the DACIS 103 toreceive a disparate live media output stream manifest to begin orcontinue playback. The first manifest request may comprise one or moreparameters, such as universal resource locators and/or identifiersreferencing records for one or more live input streams or one or morepre-encoded media assets in the CPDS 107, a plurality of client-specificparameters, and a plurality of client-specified attributes derived froma user interaction with the consumer device, such as the consumer device110 a. The plurality of client-specific parameters may comprise userpreferences and identifiers, client device preferences and identifiers,and one or more rules governed by geolocation data and current positionof playback of a first disparate live media output stream at theconsumer device, such as the consumer device 110 a. The plurality ofclient-specified attributes may comprise the user interaction withinteractive content in a customized first programming content and atargeted first non-programming content, and a preference for a typeand/or category of the targeted first non-programming content and/or thecustomized first programming content. The user interaction with theinteractive content may comprises a selection to exclude the targetedfirst non-programming content and/or the customized first programmingcontent, a selection to include a subset of the targeted firstnon-programming content and/or the customized first programming content,and a selection to include all of the targeted first non-programmingcontent and/or the customized first programming content within one ormore specified non-programming content locations.

In case the first manifest request is for a first disparate live mediaoutput stream, the PEM 115 transmits the one or more parameters in thefirst manifest request to the stream selection service 142. The streamselection service 142 may determine live input streams and/orpre-encoded media assets, based on the one or more parameters in thefirst manifest request and in repository of schedules, rights, and userpreferences database 144. The stream selection service 142 may transmitthe determined identifiers or URLs of the live input streams and/orpre-encoded media assets to the PEM 115. The PEM 115 may then transmitthe first manifest request to the CPDS 107 to retrieve metadata for thedetermined live input streams and/or pre-encoded media assets. Themetadata may include, for example ad break locations, overlaymarkers/triggers, SCTE35 markers, and content duration.

The PEM 115 of the DACIS 103 may further transmit the received firstmanifest request to the CPDS 107 based on the selected one or more liveinput streams and/or one or more pre-encoded media assets. The PEM 115may receive the indexed metadata, for example non-programmingindicators, such as ad break locations, graphical treatment indicators,such as overlay markers/triggers, programming indictors, such as SCTE35markers and content duration, from the CPDS 107.

The PEM 115 may further identify the one or more content placementopportunities defined by the metadata associated with the one or morelive input streams and/or one or more pre-encoded media assets. The PEM115 may further receive additional content, such as targeted firstnon-programming content from the Ad decisioning server 106 a, andcustomized first programming content to match one or morepersonalization parameters from the CDS 105.

The PEM 115 may be configured to generate the first programming schedule111 for a first client device, such as the client device 132 a, based onselected one or more live input streams and/or the one or morepre-encoded media assets, the associated indexed metadata, and thedetermined first additional content. The generated first programmingschedule 111 may be delivered to the stream publishing engine 114. Thestream publishing engine 114 may be configured to select the one or morelive input stream manifests and/or the one or more pre-encoded mediaasset manifests published in the content delivery system 130. Theindexing and storage system 116 may be configured to index the pluralityof media segments indicated by the one or more pre-encoded media assetmanifests and the one or more live input stream manifests, theassociated indexed metadata, the targeted first non-programming content,and the customized first programming content may be indexed based on thefirst programming schedule 111 generated for the first client device,for example the client device 132 a. The stream publishing engine 114may be further configured to publish the first disparate live mediaoutput stream manifest for the first client device, for example theclient device 132 a. The DACIS 103 may transmit the published firstdisparate live media output stream manifest to the media player of thefirst client device for playback of the first disparate live mediaoutput stream, for example the disparate live media output stream 117 a.

In accordance with an embodiment, the PEM 115 may receive a userinteraction from the media player of the first client device, forexample the client device 132 a. The user interaction may correspond toone of a desired selection corresponding to the user interaction withone or more interactive elements, or a default selection correspondingto a non-interaction of the user with the customized first programmingcontent and/or the targeted first non-programming content in the firstdisparate live media output stream 117 a played back by the mediaplayer. Based on the user interaction with the interactive content, thePEM 115 of the DACIS 103 may be configured to modify the remainingportion of the first programming schedule 111 that generates the firstdisparate live media output stream 117 a corresponding to the firstmanifest request generated by the first client device, such as theclient device 132 a.

In accordance with another aspect (regarding personalized insertion ofplaylist of non-programming content and/or programming content) of thedisclosure, the DACIS 103 may be configured to receive the firstmanifest request from the first client device, such as a client device132 a, to begin or continue playback of a first disparate live mediaoutput stream, for example the disparate live media output stream 117 a.In such embodiment, in addition to the plurality of client-specificparameters described above, the plurality of client-specified attributesmay comprise a preference for a given type and/or category (orcategories) of targeted non-programming content or customizedprogramming content, and a possible time constraint (duration) to fillwith content. Thereafter, in similar manner as described above, the PEM115 may transmit the one or more parameters in the first manifestrequest to the stream selection service 142. The stream selectionservice 142 may determine live input streams and/or pre-encoded mediaassets, based on the one or more parameters in the first manifestrequest and in repository of schedules, rights, and user preferencesdatabase 144. The stream selection service 142 may transmit thedetermined identifiers or URLs of the live input streams and/orpre-encoded media assets to the PEM 115. The PEM 115 may then transmitthe first manifest request to the CPDS 107 to retrieve metadata for thedetermined live input streams and/or pre-encoded media assets. Themetadata may include, for example, categories to which content isassigned to (for example, “basketball”, “sports”, “Knicks”), in additionto ad break locations, overlay markers/triggers, SCTE35 markers, andcontent duration.

The PEM 115 may identify one or more content placement opportunitiesdefined by the metadata and may transmit a request to the CDS 105 todetermine the customized first programming content from the CPDS 107 formatching one or more personalization parameters. Accordingly, the PEM115 may generate the first programming schedule 111 defining locationsand types of one or more decision points defined by the one or morecontent placement opportunities in the indexed metadata. The one or moredecision points may define personalized content preferences, skipping ofpersonalized content and moving to default content, and approval ordisapproval of the personalized content. The remaining operations may besimilar to the just-in-time insertion of non-programming content and/orprogramming content.

In accordance with another aspect (regarding stream failover) of thedisclosure, the DACIS 103 may be configured to receive the firstmanifest request from the first client device, such as a client device132 a. The first manifest request may comprise one or more parameters,as described above. The PEM 115 may transmit the received first manifestrequest that comprises the one or more parameters to the streamselection service 142. The stream selection service 142 may determine ifthe set of criteria associated with the first disparate live mediaoutput stream is satisfied. The set of criteria may includeaccessibility of the first disparate live media output stream, update ofthe first disparate live media output stream and/or compatibility of thefirst disparate live media output stream having media and/or a manifestwith the first manifest request. The stream selection service 142 may befurther configured to determine the one or more live input streamsand/or one or more pre-encoded media assets based on the one or moreparameters in the first manifest request, and additional parametersretrieved from the repository of schedules, rights, and user preferencesdatabase 144. The stream selection service 142 may be further configuredto determine the one or more live input streams and/or one or morepre-encoded media assets based on rules provided by a streamowner/operator (such as a regional blackout for the first client deviceleading to an alternative stream to watch) and user preferences (thatexclude certain categories) defined in the repository of schedules,rights, and user preferences database 144.

When the set of criteria associated with the first disparate live mediaoutput stream is not satisfied, the stream selection service 142 mayselect a pre-encoded asset indicated in the first manifest request tocontinue playback as the first disparate live media output stream. ThePEM 115 may receive the universal resource locators and/or identifiersthat reference records for the selected one or more live input streamsor alternate one or more pre-encoded media assets based on the one ormore parameters and additional parameters retrieved from the repositoryof schedules, rights, and user preferences database 144. The PEM 115 mayfurther transmit the received first manifest request to the CPDS 107based on the selected one or more live input streams or alternate one ormore pre-encoded media assets. The PEM 115 may further receive thealternate metadata for the alternate additional content from the CPDS107. The metadata may include, for example, Ad break locations, overlaymarkers/triggers, SCTE35 markers/triggers, content duration, and one ormore decision points. The alternate metadata may further include alocation to transition from the first additional content to thealternate additional content. Thereafter, a placement of alternateadditional content within the first disparate live media output streammanifest may be determined based on the associated indexed metadata andthe alternate metadata. The PEM 15 may further generate the alternateprogramming schedule for the first client device, such as the clientdevice 132 a, based on the alternate additional content and alternatemetadata. Accordingly, the stream selection service 142 may publish thefinal disparate live output stream manifest for the first client device,such as the client device 132 a, based on the generated alternateprogramming schedule.

In accordance with another aspect (regarding dynamic playout buffer fordisparate live media output stream) of the disclosure, the PEM 115 ofthe DACIS 103 may be configured to publish the first programmingschedule 111 that references at least one or more pre-encoded mediaassets and/or one or more live input streams. The published firstprogramming schedule may comprise one or more playout buffer featuresenabled via one or more constraints and rights.

A first playout buffer feature of the one or more playout bufferfeatures may correspond to a minimum playout buffer size. The minimumplayout buffer size indicates a minimum number of media segments thatrepresents the one or more pre-encoded media assets and/or the one ormore live input streams, as defined in the first programming schedule111. A second playout buffer feature of the one or more playout bufferfeatures may correspond to a maximum playout buffer size. The maximumplayout buffer size indicates a maximum number of media segments thatrepresents the one or more pre-encoded media assets and/or the one ormore live input streams, as defined in the first programming schedule111. A third playout buffer feature of the one or more playout bufferfeatures may correspond to a default playout buffer size. The defaultplayout buffer size indicates a pre-specified number of media segmentsthat represents the one or more pre-encoded media assets and/or the oneor more live input streams, as defined in the first programming schedule111. In accordance with an embodiment, the PEM 115 of the DACIS 103 maybe configured to determine a fourth playout buffer feature based on areference to the repository of schedules, rights, and preferencesdatabase 144 or a third-party database by the first programming schedule111.

In accordance with an embodiment, the stream publishing engine 114 inthe DACIS 103 may be configured to receive a request that may compriseat least a stream identifier and at least an additional parameter. Thestream publishing engine 114 may query the indexing and storage system116 based on the received request. Accordingly, the stream publishingengine 114 may determine the first programming schedule 111, manifestdata and indexed metadata associated with the query from the indexingand storage system 116. The manifest data and the indexed metadata maycorrespond to one or more media segments associated with the streamidentifier to be inserted to the first disparate live media outputstream manifest in accordance with the first programming schedule 111,the playout buffer feature from the one or more playout buffer features,and at least the additional parameter.

In accordance with an embodiment, the stream publishing engine 114 mayfail to validate that the one or more media segments associated with thestream identifier are eligible for the playout and accordingly, an errornotification may be generated. In accordance with another embodiment,the stream publishing engine 114 may validate that the one or more mediasegments associated with the stream identifier are eligible for theplayout, and further validate that the one or more media segmentsassociated with the stream identifier are eligible in accordance withthe fourth playout buffer feature enabled via the one or moreconstraints and rights. Accordingly, the stream publishing engine 114may set the default playout buffer duration for the one or more mediasegments and proceed to insert the manifest data and indexed metadata ofone or more media segments associated with the stream identifier to thefirst disparate live media output stream manifest in accordance with thedefault playout buffer duration.

In accordance with another embodiment, when the stream publishing engine114 fails to validate that the one or more media segments associatedwith the stream identifier are eligible in accordance with the fourthplayout buffer feature, the stream publishing engine 114 may furthercheck the additional parameter. In accordance with a first exemplaryscenario, when the one or more media segments associated with the streamidentifier are eligible in accordance with the fourth playout bufferfeature and at least the additional parameter comprises both of the useridentifier and the altered playout buffer duration flag, the streampublishing engine 114 may query the repository of schedules, rights, andpreferences database 144 based on the user identifier. Accordingly, thestream publishing engine 114 may receive a permissible playout bufferduration, set the playout buffer duration according to the receivedpermissible playout buffer duration, and proceed to insert the manifestdata and indexed metadata of one or more media segments associated withthe stream identifier to the first disparate live media output streammanifest in accordance with the playout buffer duration according to thereceived permissible playout buffer duration. In accordance with asecond exemplary scenario, when the one or more media segmentsassociated with the stream identifier are eligible in accordance withthe fourth playout buffer feature and at least the additional parametercomprises a desired playout buffer duration for the one or more mediasegments associated with the stream identifier, the stream publishingengine 114 may set the playout buffer duration for the one or more mediasegments based on the desired playout buffer duration. When the desiredplayout buffer duration exceeds the maximum playout buffer duration, thestream publishing engine 114 may set the playout buffer duration for theone or more media segments in accordance with the second playout bufferfeature, and proceed to insert the manifest data and indexed metadata ofone or more media segments associated with the stream identifier to thefirst disparate live media output stream manifest in accordance with thesecond playout buffer feature. When the desired playout buffer durationfails to exceed the maximum playout buffer duration, the streampublishing engine 114 may proceed to insert the manifest data andindexed metadata of one or more media segments associated with thestream identifier to the first disparate live media output streammanifest in accordance with the playout buffer duration based on thedesired playout buffer duration. In accordance with a third exemplaryscenario, when the one or more media segments associated with the streamidentifier are eligible for the playout and the additional parameterdoes not comprise the altered playout buffer duration flag or thedesired playout buffer duration, the stream publishing engine 114 mayproceed to insert the manifest data and indexed metadata of one or moremedia segments associated with the stream identifier to the firstdisparate live media output stream manifest in accordance with thedefault live window duration.

Once the manifest data and indexed metadata of one or more mediasegments associated with the stream identifier is inserted to the firstdisparate live media output stream manifest in accordance with the oneor more playout buffer features and at least the additional parameter,as described above in accordance with the various embodiments andexemplary scenarios, the stream publishing engine 114 may generate thefirst disparate live media output stream based on one of a pre-definedconversion modes. The pre-defined conversion modes may correspond topre-encoded media assets to live stream mode, pre-encoded media assetsto live stream mode with scalable architecture, a live stream to livestream mode, and a mixed mode corresponding to switching betweenpre-encoded media assets and live streams. The stream publishing engine114 may further playout the generated first disparate live media outputstream to be viewed at one or more of the client devices 132 a, . . . ,132 n.

FIG. 2 illustrates segmentation of live input streams and pre-encodedmedia assets for the first programming schedule 111 or the alternateprogramming schedule 113 for publishing a disparate per-client livemedia output stream based on dynamic insertion of targetednon-programming content and customized programming content by the DACIS103 of FIG. 1B, and for providing a dynamic playout buffer for disparatelive media output stream, in accordance with exemplary embodiments ofthe disclosure. Referring to the exemplary arrangement of FIG. 2, thereis shown a first live input stream 202, a first pre-encoded media asset204, and a second live input stream 206. There is also shown a targetedfirst non-programming content 208 placed after the first live inputstream 202, and a customized first programming content 210 placed afterthe first pre-encoded media asset 204. The first live input stream 202may be segmented into a first set of video segments 202 a, 202 b, 202 c,. . . , 202 n. Similarly, the first pre-encoded media asset 204 and thesecond live input stream 206 may also be segmented into second set ofvideo segments 204 a, 204 b, 204 c, . . . , 204 n, and third set ofvideo segments 206 a, 206 b, 206 c, . . . , 206 n respectively. By wayof example, the segmentation may be executed by a segmenting system (forexample a live stream encoder/packager and/or a content encoder/packager(not shown)) during a preparation stage of the media assets. The encodestage may create various quality levels and the package stage segmentsthe content into the short segments, and produces the correct format,such as TS, fMP4, or CMAF and encrypts the media content to preventpiracy. In accordance with an embodiment, the segments of the first setof video segments 202 a, 202 b, 202 c, . . . , 202 n, the second set ofvideo segments 204 a, 204 b, 204 c, . . . , 204 n, and third set ofvideo segments 206 a, 206 b, 206 c, . . . , 206 n, may be segmented intoconsistent length, for example, 10 seconds segments. It may beadvantageous to have a consistent and smaller file size of segments tobe able to quickly push to the content delivery system 130, and also forquick downloading by a media player at the end-user side, such as on theplurality of consumer devices 110 a, . . . , 110 n.

It should be understood by those skilled in the art that various changesmay be made and segments of different file sizes (or length) may be usedwithout departure from the scope of the present disclosure. Further,other streaming protocols may require a different processing of mediacontent. Thus, the scope of the disclosure should not be limited to theprocessing or preparation of media content to allow delivery usingdifferent delivery methods, streaming protocols, or distribution system,known in the art. Further, instead of the live input streams andpre-encoded media asset arranged, as shown, different arrangements perthe first programming schedule 111 or the alternate programming schedule113 may be possible with respect to interstitial content items, such asthe targeted first non-programming content 208 and the customized firstprogramming content 210.

The insertion of the live input stream manifests, pre-encoded mediaasset manifests, the targeted first non-programming content 208 and thecustomized first programming content 210 may be done on-the-fly based ondynamic scheduling by the PEM 115 that generates the first programmingschedule 111 or the alternate programming schedule 113. The insertionmay be driven by real time or near-real time content context analysis,user-selection on the consumer devices 110 a, . . . , 110 n, or drivenby external data received from the external data source 120. The PEM 115in association with the stream selection service 142 may be configuredto insert live input streams, such as the first live input stream 202and the second live input stream 206, or pre-stored media assets, suchas the first pre-encoded media asset 204, the targeted firstnon-programming content 208 and the customized first programming content210, in an existing disparate live media output stream based onmanipulation of a manifest the existing disparate live media outputstream, such as an existing channel.

In accordance with an embodiment, each segment of the first set of videosegments 202 a, 202 b, 202 c, . . . , 202 n, the second set of videosegments 204 a, 204 b, 204 c, . . . , 204 n, and third set of videosegments 206 a, 206 b, 206 c, . . . , 206 n, may be further processed tobe stored at various quality levels, and content encryption modes forthe purposes of adaptive bitrate streaming and digital rightsmanagement, for example, the video segment 202 a may be stored in aplurality of quality levels, for example, high definition (HD), highdynamic range (HDR) video, or different quality levels in accordancewith specified pixel resolutions, bitrates, frame rates, and/or samplefrequencies. As each of the media content, such as 202 to 206, areencoded, segmented, and stored with the plurality of quality levels in amedia content master storage system. The media content may be re-used tocreate new channels, such as a new disparate live media output stream,without having to re-encode a selected live input stream or apre-encoded media asset when a new disparate live media output stream iscreated using the live input streams or a pre-encoded media asset.

For the sake of brevity, and with reference to FIG. 2, there is shown anexample of publishing the first or the updated (or alternate) disparatelive media output streams based on dynamic insertion of targetednon-programming content and customized programming content by the DACIS103 of FIG. 1B. It is to be understood that media packaging fordifferent delivery methods (such as analog terrestrial broadcast,digital terrestrial broadcast, direct-to-home satellite broadcast,cable, other Internet Protocol (IP)-based delivery methods, over-the-toptelevision (OTT)), different streaming protocols, or distributionsystem, may be different. The media content may be prepared to be viewedone or more of the plurality of consumer devices 110 a, . . . , 110 n,based on at least the desired delivery method, delivery conditions,content protection requirements, to satisfy operational and technicalrequirements, as needed. The operational and technical requirements mayinclude, but are not limited to, media encoding, media segmentation,programming schedule (or manifest) creation or manipulationrequirements, desired media encryption, and/or metadata signalingrequirements. For example, in certain scenarios and for certain mediacontent delivery methods, network bandwidth, network conditions, ordevice-type where media content is to be consumed may not be variable orknown in advance. In such a case, creating different quality levels forsame media content may not be required. Further, based on differentoperational and technical requirements, publishing of disparate livemedia output stream may be different. The media content that is preparedand distributed may include both the programming content, such aslong-form presentations, short-form presentations, news or sportingevents; and non-programming content, such as paid advertisements, publicservice advertisements, or promotional material.

FIG. 3 illustrates an exemplary scenario associated with publishing adisparate live media output stream by the DACIS 103 of FIG. 1B, inaccordance with an exemplary embodiment of the disclosure. Referring tothe exemplary scenario 300, there are illustrated two disparate livemedia output streams 302 and 304 published for two users associated withthe client devices 132 a and 132 n, respectively. The disparate livemedia output stream 302 may be existing disparate live media outputstream for the client device 132 a. The disparate live media outputstream 304 may be a disparate per-client live media output streampublished based on dynamic insertion of targeted non-programming contentand customized programming content by the DACIS 103 of FIG. 1B for theclient device 132 n.

The live NBA game may be scheduled to start at 8:00 pm. However, a userassociated with the client device 132 n tunes in early to watch the NBAgame, for example at 7:15 pm. However, the user may not be interested inwatching the end of the current programming media content. In such acase, the PEM 115 in the DACIS 103 may determine targetednon-programming content, such as sports items ads, and customizedprogramming content, such as NBA highlights of previous game andgenerates the alternate programming schedule 113. Accordingly, thestream publishing engine 114 in the DACIS 103 may publish an alternatedisparate live media output stream 117 n for the client device 132 n. At8:00 pm, the DACIS 103 may switch back to the live NBA game scheduled at8:00 pm.

FIGS. 4A to 4D depict flowcharts illustrating exemplary operations forpublishing a disparate per-client live media output stream based ondynamic insertion of targeted non-programming content and customizedprogramming content in the media packaging and distribution system 102of FIG. 1B, in accordance with an exemplary embodiment of thedisclosure. Specifically, flowcharts 400A and 400B collectively depictsa method for just-in-time insertion of non-programming content and/orprogramming content, in accordance with an embodiment of the disclosure.Flowchart 400C depicts a method for personalized insertion ofnon-programming content and/or programming content, in accordance withan embodiment of the disclosure. Flowchart 400E depicts a method forstream failover, in accordance with an embodiment of the disclosure.

Referring to FIGS. 4A and 4B, flowcharts 400A and 400B collectivelydepicts a method for just-in-time insertion of non-programming contentand/or programming content, in accordance with an embodiment of thedisclosure.

At 402A, a first manifest request may be received from a first clientdevice. In accordance with an embodiment, the DACIS 103 may beconfigured to receive the first manifest request from the first clientdevice, such as a client device 132 a, to begin or continue playback ofa first disparate live media output stream, for example the disparatelive media output stream 117 a. The first manifest request may compriseone or more parameters. Examples of the one or more parameters mayinclude, but are not limited to, universal resource locators and/oridentifiers referencing records for existing one or more live inputstreams or one or more pre-encoded media assets in the CPDS 107, aplurality of client-specific parameters, and a plurality ofclient-specified attributes derived from a user interaction with thefirst client device, such as the client device 132 a. Examples of theplurality of client-specific parameters may include, but are not limitedto, user preferences and identifiers, client device preferences andidentifiers, and one or more rules governed by geolocation data andcurrent position of playback of a first disparate live media outputstream, such as the disparate live media output stream 117 a, at thefirst client device, such as the client device 132 a. In an embodiment,the client-specified attributes derived from a user interaction with thefirst client device may include, but are not limited to, the userinteraction with interactive content in a customized first programmingcontent and a targeted first non-programming content, and a preferencefor a type and/or category of the targeted first non-programming contentand/or the customized first programming content. The user interactionwith the interactive content may comprise, for example, a selection toexclude the targeted first non-programming content and/or the customizedfirst programming content, a selection to include a subset of thetargeted first non-programming content and/or the customized firstprogramming content, and a selection to include all of the targetedfirst non-programming content and/or the customized first programmingcontent within one or more specified non-programming content locations.

At 404A, the received first manifest request that comprises one or moreparameters may be transmitted to the stream selection service 142. In anembodiment, the PEM 115 of the DACIS 103 may be configured to transmitthe received first manifest request that comprises the one or moreparameters to the stream selection service 142.

In an embodiment, based on the received first manifest request, thestream selection service 142 may be configured to select one or morelive input streams and/or one or more pre-encoded media assets based onthe one or more parameters and additional parameters retrieved from therepository of schedules, rights, and user preferences database 144.Accordingly, the stream selection service 142 may be configured toreturn universal resource locators and/or identifiers that referencerecords for the selected one or more live input streams and/or one ormore pre-encoded media assets to the PEM 115.

At 406A, the universal resource locators and/or identifiers thatreference records for the selected one or more live input streams and/orone or more pre-encoded media assets based on the one or more parametersand additional parameters retrieved from the repository of schedules,rights, and user preferences database 144 may be received. In anembodiment, the PEM 115 of the DACIS 103 may be configured to receivethe universal resource locators and/or identifiers that referencerecords for the selected one or more live input streams and/or one ormore pre-encoded media assets based on the one or more parameters andadditional parameters retrieved from the repository of schedules,rights, and user preferences database 144.

At 408A, the received first manifest request may be transmitted to theCPDS 107 based on the selected one or more live input streams and/or oneor more pre-encoded media assets. In an embodiment, the PEM 115 of theDACIS 103 may be configured to transmit the received first manifestrequest to the CPDS 107 based on the selected one or more live inputstreams and/or one or more pre-encoded media assets.

In an embodiment, based on the received first manifest request, the CPDS107 may be configured to retrieve indexed metadata, for example,non-programming indicators, such as ad break locations, graphicaltreatment indicators, such as overlay markers/triggers, programmingindictors, such as SCTE35 markers and content duration. Accordingly, theCPDS 107 may be configured to return the indexed metadata to the PEM115.

At 410A, the indexed metadata may be received from the CPDS 107. In anembodiment, the PEM 115 of the DACIS 103 may be configured to receivethe indexed metadata from the CPDS 107. Examples of the indexed metadatamay include, but are not limited to, non-programming indicators, such asad break locations, graphical treatment indicators, such as overlaymarkers/triggers, programming indictors, such as SCTE35 markers andcontent duration, as described above.

At 412A, one or more content placement opportunities defined by themetadata associated with the one or more live input streams and/or oneor more pre-encoded media assets may be identified. In an embodiment,the PEM 115 of the DACIS 103 may be configured to identify the one ormore content placement opportunities defined by the metadata associatedwith the one or more live input streams and/or one or more pre-encodedmedia assets. Examples of the one or more content placementopportunities may include, but are not limited to, non-programmingindicators, such as ad break locations, graphical treatment indicators,such as overlay markers/triggers, programming indictors, such as SCTE35markers and personalized content opportunity. In an embodiment, for theidentified one or more content placement opportunities, the PEM 115 ofthe DACIS 103 may be configured to determine additional content, such asnon-programming content (such as advertisements), personalizedprogramming content (such as promotional content), graphical treatment(such as overlays), and one or more decision point locations.

At 414, a request may be transmitted to the Ad decisioning server 106 ato determine targeted first non-programming content. In an embodiment,the PEM 115 of the DACIS 103 may be configured to transmit the requestto the Ad decisioning server 106 a to determine the targeted firstnon-programming content.

In an embodiment, based on the request, the Ad decisioning server 106 amay be configured to identify the targeted first non-programmingcontent, such as an advertising or a graphical treatment content, to bescheduled in one or more content placement opportunities, based on theone or more parameters. In an embodiment, the Ad decisioning server 106a may be configured to identify the targeted first non-programmingcontent based on execution of a non-programming content service based onrules and conditions defined in additional parameters of the repositoryof schedules, rights, and user preferences database 144, and the one ormore parameters defined in the first manifest request. Accordingly, theAd decisioning server 106 a may be configured to transmit the identifiedtargeted first non-programming content to the PEM 115 of the DACIS 103.

At 416, the targeted first non-programming content may be received fromthe Ad decisioning server 106 a. In an embodiment, the PEM 115 of theDACIS 103 may be configured to receive the targeted firstnon-programming content from the Ad decisioning server 106 a.

At 418, a request may be transmitted to the CDS 105 to determine acustomized first programming content to match one or morepersonalization parameters. In an embodiment, the PEM 115 of the DACIS103 may be configured to transmit the request to the CDS 105. The CDS105 may determine a customized first programming content to match one ormore personalization parameters.

In an embodiment, based on the request, the CDS 105 may be configured toidentify the customized first programming content based on the one ormore parameters in the first manifest request, and the rules andconditions defined in the additional parameters of the repository ofschedules, rights, and user preferences database 144. Accordingly, theCDS 105 may be configured to transmit the identified customized firstprogramming content to the PEM 115 of the DACIS 103.

At 420, the customized first programming content may be received fromthe CDS 105. In an embodiment, the PEM 115 of the DACIS 103 may beconfigured to receive the customized first programming content from theCDS 105.

At 422, a first additional content comprising the customized firstprogramming content and the targeted first non-programming content maybe determined for the first client device based on the one or moreparameters and the associated indexed metadata. In an embodiment, thePEM 115 of the DACIS 103 may be configured to determine the firstadditional content comprising the customized first programming content,received from the CDS 105, and the targeted first non-programmingcontent, received from the Ad decisioning server 106 a. The firstadditional content may be determined for the first client device, suchas the client device 132 a, based on the one or more parameters and theassociated indexed metadata, received from the CPDS 107.

At 424, a first programming schedule 111 may be generated for the firstclient device based on the selected one or more live input streamsand/or the one or more pre-encoded media assets, the associated indexedmetadata, and the determined first additional content. In an embodiment,the PEM 115 of the DACIS 103 may be configured to generate the firstprogramming schedule 111 for the first client device, such as the clientdevice 132 a, based on selected one or more live input streams and/orthe one or more pre-encoded media assets, the associated indexedmetadata, and the determined first additional content.

In accordance with an embodiment, the generated first programmingschedule 111 may not include the first additional content, in accordancewith the one or more parameters in the first manifest request. Inaccordance with another embodiment, the generated first programmingschedule 111 may include the first additional content, in accordancewith the one or more parameters in the first manifest request. Inaccordance with another embodiment, the generated first programmingschedule 111 may include a subset of the first additional content, inaccordance with the one or more parameters in the first manifestrequest.

In accordance with an embodiment, the first additional content scheduledto be inserted, may be inserted into, for example, one or morepre-encoded assets in accordance with appropriate markers. Theappropriate markers may be defined in the metadata of the one or morepre-encoded assets, and rules and conditions defined in the repositoryof schedule, rights, and user preferences database 144.

In accordance with an embodiment, the generated first programmingschedule 111 may define locations and types of one or more decisionpoints defined by the one or more content placement opportunities in theindexed metadata. The one or more decision points may be included in thefirst programming schedule 111. Within the first programming schedule111, the one or more decision points may define various types of thedecision points, for example, an Ad preference, skip next ad, skipfuture ads, watch ads immediately instead of at future ad locations, orpersonalized content preferences.

In an exemplary embodiment, the one or more pre-encoded media assets arescheduled and the one or more decision points, defined by the one ormore content placement opportunities, are inserted in the firstprogramming schedule 111. In such exemplary embodiment, the firstprogramming schedule 111 may be configured to control the one or morepre-encoded media asset manifests to be published as, for example, thefirst disparate live media output stream manifest. Further, the firstprogramming schedule 111 may include, for example, segments, markers,the one or more content placement opportunities, up to and includingnext available decision point.

At 426, the first programming schedule 111 may be delivered to thestream publishing engine 114. In accordance with an embodiment, the PEM115 in the DACIS 103 may be configured to deliver the first programmingschedule 111 to the stream publishing engine 114.

At 428, one or more live input stream manifests and/or one or morepre-encoded media asset manifests published in the content deliverysystem 130 may be selected. In accordance with an embodiment, the streampublishing engine 114 in the DACIS 103 may be configured to select theone or more live input stream manifests and/or the one or morepre-encoded media asset manifests published in the content deliverysystem 130.

At 430, a plurality of media segments indicated by the one or morepre-encoded media asset manifests and the one or more live input streammanifests, the associated indexed metadata, the targeted firstnon-programming content, and the customized first programming contentmay be indexed based on the first programming schedule 111 generated forthe first client device. In accordance with an embodiment, the indexingand storage system 116 may be configured to index the plurality of mediasegments indicated by the one or more pre-encoded media asset manifestsand the one or more live input stream manifests, the associated indexedmetadata, the targeted first non-programming content, and the customizedfirst programming content may be indexed based on the first programmingschedule 111 generated for the first client device, for example theclient device 132 a.

At 432, a first disparate live media output stream manifest for thefirst client device may be published based on insertion of the selectedone or more live input stream manifests and/or the one or morepre-encoded media asset manifests, the associated indexed metadata, andthe determined first additional content, into the first disparate livemedia output stream manifest, in accordance with the first programmingschedule 111 generated for the first client device. In accordance withan embodiment, the stream publishing engine 114 in the DACIS 103 may beconfigured to publish the first disparate live media output streammanifest for the first client device, for example the client device 132a. The publication may be based on insertion of the selected one or morelive input stream manifests and/or the one or more pre-encoded mediaasset manifests, the associated indexed metadata, and the determinedfirst additional content, into the first disparate live media outputstream manifest, in accordance with the first programming schedule 111generated for the first client device, for example the client device 132a.

At 434, the published first disparate live media output stream manifestmay be transmitted to a media player of the first client device forplayback of the first disparate live media output stream, for examplethe disparate live media output stream 117 a. In accordance with anembodiment, the DACIS 103 may be configured to transmit the publishedfirst disparate live media output stream manifest to the media player ofthe first client device for playback of the first disparate live mediaoutput stream, for example the disparate live media output stream 117 a.In accordance with an embodiment, the first disparate live media outputstream manifest for the first client device, for example the clientdevice 132 a, may be generated based on one of a pre-defined conversionmodes. The pre-defined conversion modes may correspond to conversion ofpre-encoded media assets to live stream mode, pre-encoded media assetsto live stream mode with scalable architecture, a live stream to livestream mode, and a mixed mode corresponding to switches betweenpre-encoded media assets and live streams.

In accordance with an embodiment, the published first disparate livemedia output stream manifest may be delivered to the first clientdevice, for example the client device 132 a. Accordingly, the mediaplayer of the first client device, for example the client device 132 a,may begin or continue playback of the first disparate live media outputstream 117 a. Further, the media player, during playback of the firstdisparate live media output stream 117 a at the first client device, forexample the client device 132 a, presents one or more decision pointsdefined by the interactive content to initiate a user interaction at thefirst client device, for example the client device 132 a.

In accordance with an embodiment, during the playback, in case adecision point exists, is enabled, and presented by the first clientdevice, for example the client device 132 a, the user of the clientdevice 132 a may interact with one or more interactive elements at thedecision point and influence (or modify) remaining first disparate livemedia output stream 117 a.

For example, in an embodiment of just-in-time non-programming contentinsertion, at the one or more decision points, the user interactioncorresponds to one of a desired selection corresponding to the userinteraction with one or more interactive elements, or a defaultselection corresponding to non-interaction of a user with the customizedfirst programming content and/or the targeted first non-programmingcontent in the first disparate live media output stream 117 a playedback by the media player. In another example, in an embodiment ofpersonalized content playlist, at the one or more decision points, theuser interaction corresponds to one of exclusion of the targeted firstnon-programming content or the customized first programming content andreplacement by default content, selection of alternate customized firstprogramming content, selection of a subsequent second programmingcontent, approval or disapproval of the selected customized firstprogramming content, exclusion of subsequent second non-programmingcontent for a remaining portion of the first disparate live media outputstream 117 a played back by the media player, selection of one or moretargeted first non-programming content of a specific category, orviewing of some or all of the targeted first non-programming contentimmediately to avoid some or all of the targeted first non-programmingcontent for the remaining portion of the first disparate live mediaoutput stream played back by the media player.

At 436, the user interaction may be received that corresponds to one ofa desired selection corresponding to the user interaction with one ormore interactive elements, or a default selection corresponding to anon-interaction of the user with the customized first programmingcontent and/or the targeted first non-programming content in the firstdisparate live media output stream 117 a played back by the mediaplayer. In accordance with an embodiment, the PEM 115 of the DACIS 103may be configured to receive the user interaction may be received. Theuser interaction may correspond to one of a desired selectioncorresponding to the user interaction with one or more interactiveelements, or a default selection corresponding to a non-interaction ofthe user with the customized first programming content and/or thetargeted first non-programming content in the first disparate live mediaoutput stream 117 a played back by the media player.

At 438, a remaining portion of the first programming schedule 111 thatgenerates the first disparate live media output stream 117 acorresponding to the first manifest request generated by the firstclient device, such as the client device 132 a, may be modified based onthe user interaction with the interactive content. In accordance with anembodiment, the PEM 115 of the DACIS 103 may be configured to modify theremaining portion of the first programming schedule 111 that generatesthe first disparate live media output stream 117 a corresponding to thefirst manifest request generated by the first client device, such as theclient device 132 a, based on the user interaction with the interactivecontent.

At 440, a desired selection or the default selection may be transmittedto an external storage system that is the repository of schedules,rights, and user preferences database 144. In accordance with anembodiment, the first client device, for example the client device 132a, may be configured to transmit the desired selection or the defaultselection to the external storage system that is the repository ofschedules, rights, and user preferences database 144.

In accordance with an embodiment, the user interaction ornon-interaction result may be sent to future client manifest requests toinfluence the remainder of the first disparate live media output stream117 a. This may allow for a user choice, such as to skip an ad, toresult with another manifest request to the DACIS 103 to update theexisting first disparate live media output stream 117 a with theintended behavior and affect playback of the first disparate live mediaoutput stream 117 a within the first client device.

Referring to FIG. 4C, flowchart 400C depicts a method for personalizedinsertion of playlist of non-programming content and/or programmingcontent, in accordance with an embodiment of the disclosure.

At 402B, a first manifest request may be received from a first clientdevice. In accordance with an embodiment, the DACIS 103 may beconfigured to receive the first manifest request from the first clientdevice, such as a client device 132 a, to begin or continue playback ofa first disparate live media output stream, for example the disparatelive media output stream 117 a. The first manifest request may compriseone or more parameters. Examples of the one or more parameters mayinclude, but are not limited to, universal resource locators and/oridentifiers referencing records for existing one or more live inputstreams or one or more pre-encoded media assets in the CPDS 107, aplurality of client-specific parameters, and a plurality ofclient-specified attributes derived from a user interaction with thefirst client device, such as the client device 132 a. Examples of theplurality of client-specific parameters may include, but are not limitedto, user preferences and identifiers, client device preferences andidentifiers, and one or more rules governed by geolocation data andcurrent position of playback of a first disparate live media outputstream, such as the disparate live media output stream 117 a, at thefirst client device, such as the client device 132 a. In anotherembodiment, the client-specified attributes derived from a userinteraction with the first client device may include, but are notlimited to, a preference for a type and/or category of the targetedfirst non-programming content and/or the customized first programmingcontent, and a possible time constraint (or duration) to fill with thetargeted first non-programming content and/or the customized firstprogramming content. The user interaction with the interactive contentmay comprise, for example, a selection to exclude the targeted firstnon-programming content and/or the customized first programming content,a selection to include a subset of the targeted first non-programmingcontent and/or the customized first programming content, and a selectionto include all of the targeted first non-programming content and/or thecustomized first programming content within one or more specifiednon-programming content locations.

The user interaction with the interactive content may comprise, forexample, a selection to exclude the targeted first non-programmingcontent and/or the customized first programming content, a selection toinclude a subset of the targeted first non-programming content and/orthe customized first programming content, and a selection to include allof the targeted first non-programming content and/or the customizedfirst programming content within one or more specified non-programmingcontent locations.

At 404B, the received first manifest request that comprises one or moreparameters may be transmitted to the stream selection service 142. In anembodiment, the PEM 115 of the DACIS 103 may be configured to transmitthe received first manifest request that comprises the one or moreparameters to the stream selection service 142.

In an embodiment, based on the received first manifest request, thestream selection service 142 may be configured to select one or morelive input streams and/or one or more pre-encoded media assets based onthe one or more parameters and additional parameters retrieved from therepository of schedules, rights, and user preferences database 144.Accordingly, the stream selection service 142 may be configured toreturn universal resource locators and/or identifiers that referencerecords for the selected one or more live input streams and/or one ormore pre-encoded media assets to the PEM 115.

At 406B, the universal resource locators and/or identifiers thatreference records for the selected one or more live input streams and/orone or more pre-encoded media assets based on the one or more parametersand additional parameters retrieved from the repository of schedules,rights, and user preferences database 144 may be received. In anembodiment, the PEM 115 of the DACIS 103 may be configured to receivethe universal resource locators and/or identifiers that referencerecords for the selected one or more live input streams and/or one ormore pre-encoded media assets based on the one or more parameters andadditional parameters retrieved from the repository of schedules,rights, and user preferences database 144.

At 408B, the received first manifest request may be transmitted to theCPDS 107 based on the selected one or more live input streams and/or oneor more pre-encoded media assets. In an embodiment, the PEM 115 of theDACIS 103 may be configured to transmit the received first manifestrequest to the CPDS 107 based on the selected one or more live inputstreams and/or one or more pre-encoded media assets.

In an embodiment, based on the received request, the CPDS 107 may beconfigured to retrieve indexed metadata, for example, non-programmingindicators, such as ad break locations, graphical treatment indicators,such as overlay markers/triggers, programming indictors, such as SCTE35markers, content duration, and categories (such as, “basketball”,“sports”, “Knicks”) to which the programming content has been assigned.

At 410B, the indexed metadata may be received from the CPDS 107. In anembodiment, the PEM 115 of the DACIS 103 may be configured to receivethe indexed metadata from the CPDS 107. Examples of the indexed metadatamay include, but are not limited to, non-programming indicators, such asad break locations, graphical treatment indicators, such as overlaymarkers/triggers, programming indictors, such as SCTE35 markers andcontent duration, as described above.

At 412B, one or more content placement opportunities defined by themetadata associated with the one or more live input streams and/or oneor more pre-encoded media assets may be identified. In an embodiment,the PEM 115 of the DACIS 103 may be configured to identify the one ormore content placement opportunities defined by the metadata associatedwith the one or more live input streams and/or one or more pre-encodedmedia assets. Examples of the one or more content placementopportunities may include, but are not limited to, non-programmingindicators, such as ad break locations, graphical treatment indicators,such as overlay markers/triggers, programming indictors, such as SCTE35markers and personalized content opportunity. In an embodiment, for theidentified one or more content placement opportunities, the PEM 115 ofthe DACIS 103 may be configured to determine additional content, such asnon-programming content (such as advertisements), personalizedprogramming content (such as promotional content), graphical treatment(such as overlays), and one or more decision point locations.

At 442, a request may be transmitted to the CDS 105 to determine acustomized first programming content from the CPDS 107 for matching oneor more personalization parameters. In accordance with an embodiment,the PEM 115 of the DACIS 103 may be configured to transmit a request tothe CDS 105 to determine the customized first programming content fromthe CPDS 107 for matching one or more personalization parameters.Examples of the one or more personalization parameters may include, butare not limited to, user preferences and identifiers from the firstmanifest request or retrieved from the repository of schedules, rights,and user preferences database 144, and time constraints. The timeconstraints may be determined based on user preferences retrieved fromthe repository of schedules, rights, and user preferences database 144,a range defined in the first manifest request, and schedule tolerancesdefined in the repository of schedules, rights, and user preferencesdatabase 144, client device preferences or identifiers from the firstmanifest request or retrieved from the repository of schedules, rights,and user preferences database 144, geolocation information from thefirst manifest request or retrieved from the repository of schedules,rights, and user preferences database 144, and/or a contentrecommendation engine.

At 444, the first programming schedule 111 may be generated for thefirst client device based on the selected one or more live input streamsand/or the one or more pre-encoded media assets, the associated indexedmetadata, and the determined first additional content. In accordancewith an embodiment, the PEM 115 of the DACIS 103 may be configured togenerate the first programming schedule 111 for the first client device,such as the client device 132 a, based on the selected one or more liveinput streams and/or the one or more pre-encoded media assets, theassociated indexed metadata, and the determined first additionalcontent.

In accordance with an embodiment, the first additional content scheduledto be inserted, may be inserted into, for example, one or morepre-encoded assets in accordance with appropriate markers. Theappropriate markers may be defined in the metadata of the one or morepre-encoded assets, and rules and conditions defined in the repositoryof schedule, rights, and user preferences database 144.

In accordance with an embodiment, the generated first programmingschedule 111 may define locations and types of one or more decisionpoints defined by the one or more content placement opportunities in theindexed metadata. Such one or more decision points may be included inthe first programming schedule 111. Within the first programmingschedule 111, the one or more decision points may define personalizedcontent preferences, skipping of personalized content and moving todefault content, and approval or disapproval of the personalizedcontent.

In an exemplary embodiment, the one or more pre-encoded media assets arescheduled and the one or more decision points, defined by the one ormore content placement opportunities, are inserted in the firstprogramming schedule 111. In such exemplary embodiment, the firstprogramming schedule 111 may be configured to control the one or morepre-encoded media asset manifests to be published as, for example, thefirst disparate live media output stream manifest. Further, the firstprogramming schedule 111 may include, for example, segments, markers,the one or more content placement opportunities, up to and includingnext available decision point. Thereafter, control passes to 426 inflowchart 400B and exemplary operations till 440 may be performed insimilar manner as described above.

Referring to FIG. 4D, there is illustrated a flowchart 400D depicting amethod for stream failover, in accordance with an embodiment of thedisclosure.

At 402C, a first manifest request may be received from a first clientdevice. In accordance with an embodiment, the DACIS 103 may beconfigured to receive the first manifest request from the first clientdevice, such as a client device 132 a, to begin or continue playback ofa first disparate live media output stream, for example the disparatelive media output stream 117 a. The first manifest request may compriseone or more parameters. Examples of the one or more parameters mayinclude, but are not limited to, universal resource locators of existingone or more live input streams, identifiers referencing records forexisting one or more live input streams or one or more pre-encoded mediaassets in the CPDS 107, and a plurality of client-specific parameters.Examples of the plurality of client-specific parameters may include, butare not limited to, user preferences and identifiers, client devicepreferences and identifiers, and one or more rules governed bygeolocation data and current position of playback of a first disparatelive media output stream, such as the disparate live media output stream117 a, at the first client device, such as the client device 132 a.

At 404C, received first manifest request that comprises one or moreparameters may be transmitted to the stream selection service 142. Inaccordance with an embodiment, the PEM 115 of the DACIS 103 may beconfigured to transmit the received first manifest request thatcomprises the one or more parameters to the stream selection service142.

At 454, it may be determined that a set of criteria associated with thefirst disparate live media output stream is satisfied. In accordancewith an embodiment, the stream selection service 142 may be configuredto determine if the set of criteria associated with the first disparatelive media output stream is satisfied. The set of criteria may includean accessibility of the first disparate live media output stream, updateof the first disparate live media output stream and/or compatibility ofthe first disparate live media output stream having media and/or amanifest with the first manifest request. The stream selection service142 may be further configured to determine the one or more live inputstreams and/or one or more pre-encoded media assets based on the one ormore parameters in the first manifest request, and additional parametersretrieved from the repository of schedules, rights, and user preferencesdatabase 144. The stream selection service 142 may be further configuredto determine the one or more live input streams and/or one or morepre-encoded media assets based on rules provided by a streamowner/operator (such as a regional blackout for the first client deviceleading to an alternative stream to watch) and user preferences (thatexclude certain categories) defined in the repository of schedules,rights, and user preferences database 144.

In accordance with an embodiment, when the first disparate live mediaoutput stream is not accessible, the first disparate live media outputstream is not updated and/or the first disparate live media outputstream having media and/or manifest that is not compatible with thefirst manifest request. Further, in an absence of one or more live inputstreams, the stream selection service 142 may be configured to select apre-encoded asset indicated in the first manifest request to continueplayback as the first disparate live media output stream. In suchembodiment, control passes to operation 456. Otherwise, control passesto operation 406A of the flowchart 400A.

At 456, universal resource locators and/or identifiers that referencerecords for the selected one or more live input streams or alternate oneor more pre-encoded media assets based on the one or more parameters andadditional parameters retrieved from the repository of schedules,rights, and user preferences database 144 may be received. In accordancewith an embodiment, the PEM 115 of the DACIS 103 may be configured toreceive the universal resource locators and/or identifiers thatreference records for the selected one or more live input streams oralternate one or more pre-encoded media assets based on the one or moreparameters and additional parameters retrieved from the repository ofschedules, rights, and user preferences database 144.

At 458, a received first manifest request may be transmitted to the CPDS107 based on the selected one or more live input streams or alternateone or more pre-encoded media assets. In accordance with an embodiment,the PEM 115 of the DACIS 103 may be configured to transmit the receivedfirst manifest request to the CPDS 107 based on the selected one or morelive input streams or alternate one or more pre-encoded media assets.

At 460, alternate metadata for alternate additional content may bereceived from the CPDS 107. In accordance with an embodiment, the PEM115 of the DACIS 103 may be configured to receive the alternate metadatafor the alternate additional content from the CPDS 107. The metadata mayinclude, for example, Ad break locations, overlay markers/triggers,SCTE35 markers/triggers, content duration, and one or more decisionpoints. The alternate metadata may further include a location totransition from the first additional content to the alternate additionalcontent.

At 462, a placement of alternate additional content within the firstdisparate live media output stream manifest may be determined based onthe associated indexed metadata and the alternate metadata. Inaccordance with an embodiment, the PEM 15 of the DACIS 103 may beconfigured to determine the placement of the alternate additionalcontent within the first disparate live media output stream manifestbased on the associated indexed metadata and the alternate metadata.

At 464, an alternate programming schedule may be generated for the firstclient device based on the alternate additional content and alternatemetadata. In accordance with an embodiment, the PEM 15 of the DACIS 103may be configured to generate the alternate programming schedule for thefirst client device, such as the client device 132 a, based on thealternate additional content and alternate metadata.

At 466, a final disparate live output stream manifest may be publishedfor the first client device based on the generated alternate programmingschedule. In accordance with an embodiment, the PEM 15 of the DACIS 103may be configured to publish the final disparate live output streammanifest for the first client device, such as the client device 132 a,based on the generated alternate programming schedule.

In accordance with an embodiment, the final disparate live output streammanifest for the first client device may be generated based on one ofthe pre-defined conversion modes. The pre-defined conversion modes maycorrespond to pre-encoded media assets to live stream mode, pre-encodedmedia assets to live stream mode with scalable architecture, a livestream to live stream mode, and a mixed mode corresponding to switchesbetween pre-encoded media assets and live streams.

In accordance with an embodiment, during playout, the first additionalcontent may be transitioned to the alternate additional content based onone or more transition parameters. The one or more transition parametersmay comprise one or more parameters from the first manifest request,current state of the first disparate live media output stream manifestdetermined based on accessibility, regular update, and suitableencoding, digital rights management, and compatibility with the firstclient device, rules provided by a stream owner operator, and userpreferences defined in the repository of schedules, rights, and userpreferences database 144.

As described above in FIGS. 4A and 4B, the published final disparatelive output stream manifest may be transmitted to the media player ofthe first client device for playback of the final disparate live mediaoutput stream. Accordingly, the first client device begins or continuesthe playback of the final disparate live media output stream.

In an alternate embodiment, at 454, the stream selection service 142 maybe configured to select a second disparate live media output streamaccording to accessibility of the first disparate live media outputstream in case the set of criteria associated with the first disparatelive media output stream is not satisfied. The stream selection service142 may be configured to select the second disparate live media outputstream according to rules provided by a stream owner/operator and userpreferences defined in the repository of schedules, rights, and userpreferences database 144. The operations that follow may be performed ina similar manner, as the operations for the first disparate live mediaoutput stream are performed.

FIG. 5 is a conceptual diagram illustrating an example of a hardwareimplementation for a media packaging and distribution system 102employing a processing system for publishing a disparate per-client livemedia output stream based on dynamic insertion of targetednon-programming content and customized programming content, and forproviding a dynamic playout buffer for disparate live media outputstream, in accordance with exemplary embodiments of the disclosure.Referring to FIG. 5, the hardware implementation shown by arepresentation 500 for the media packaging and distribution system 102employs a processing system 502 for publishing a disparate per-clientlive media output stream based on dynamic insertion of targetednon-programming content and customized programming content, inaccordance with an exemplary embodiment of the disclosure, as describedherein.

In some examples, the processing system 502 may comprise one or morehardware processors 504, a non-transitory computer-readable medium 506,a bus 508, a bus interface 510, and a transceiver 512. FIG. 5 furtherillustrates the DACIS 103, the CDS 105, the CPDS 107, the streampublishing engine 114, PEM 115, indexing and storage system 116, thestream selection service 142, and the repository of schedules, rights,and user preferences database 144, as described in detail in FIGS. 1Aand 1B.

The hardware processor 504 may be configured to manage the bus 508 andgeneral processing, including the execution of a set of instructionsstored on the non-transitory computer-readable medium 506. The set ofinstructions, when executed by the processor 504, causes the mediapackaging and distribution system 102 to execute the various functionsdescribed herein for any particular apparatus. The hardware processor504 may be implemented, based on a number of processor technologiesknown in the art. Examples of the hardware processor 504 may be aReduced Instruction Set Computing (RISC) processor, anApplication-Specific Integrated Circuit (ASIC) processor, a ComplexInstruction Set Computing (CISC) processor, and/or other processors orcontrol circuits.

The non-transitory computer-readable medium 506 may be used for storingdata that is manipulated by the processor 504 when executing the set ofinstructions. The data is stored for short periods or in the presence ofpower. The non-transitory computer-readable medium 506 may also beconfigured to store data for one or more of the DACIS 103, the CDS 105,the CPDS 107, the stream publishing engine 114, PEM 115, indexing andstorage system 116, the stream selection service 142, and the repositoryof schedules, rights, and user preferences database 144.

The bus 508 is configured to link together various circuits. In thisexample, the media packaging and distribution system 102 employing theprocessing system 502 and the non-transitory computer-readable medium506 may be implemented with bus architecture, represented generally bybus 508. The bus 508 may include any number of interconnecting buses andbridges depending on the specific implementation of the media packagingand distribution system 102 and the overall design constraints. The businterface 510 may be configured to provide an interface between the bus508 and other circuits, such as, transceiver 512, and external devices,such as source device 118, external data source 120, and client devices132 a, . . . , 132 n.

The transceiver 512 may be configured to provide a communication of themedia packaging and distribution system 102 with various otherapparatus, such as the Ad decisioning servers 106 a, . . . , 106 n, theconsumer devices 110 a, . . . , 110 n, such as the client devices 132 a,. . . , 132 n, the external data source 120, and the source device 118,via the network 108. The transceiver 512 may communicate via wirelesscommunication with networks, such as the Internet, the Intranet and/or awireless network, such as a cellular telephone network, a wireless localarea network (WLAN) and/or a metropolitan area network (MAN). Thewireless communication may use any of a plurality of communicationstandards, protocols and technologies, such as Global System for MobileCommunications (GSM), Enhanced Data GSM Environment (EDGE), Long TermEvolution (LTE), wideband code division multiple access (W-CDMA), codedivision multiple access (CDMA), time division multiple access (TDMA),Bluetooth, Wireless Fidelity (Wi-Fi) (such as IEEE 802.11a, IEEE802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol(VoIP), and/or Wi-MAX.

It should be recognized that, in some embodiments of the disclosure, oneor more components of FIG. 5 may include software whose correspondingcode may be executed by at least one processor, for across multipleprocessing environments. For example, the DACIS 103, the CDS 105, theCPDS 107, the stream publishing engine 114, PEM 115, indexing andstorage system 116, the stream selection service 142, and the repositoryof schedules, rights, and user preferences database 144 may includesoftware that may be executed across a single or multiple processingenvironments.

In an aspect of the disclosure, the processor 504, the non-transitorycomputer-readable medium 506, or a combination of both may be configuredor otherwise specially programmed to execute the operations orfunctionality of the DACIS 103, the CDS 105, the CPDS 107, the streampublishing engine 114, PEM 115, indexing and storage system 116, thestream selection service 142, and the repository of schedules, rights,and user preferences database 144, or various other components describedherein, as described with respect to FIGS. 1A to 4D and FIGS. 6A and 6B.

FIGS. 6A and 6B collectively depict a flowchart illustrating exemplaryoperations for providing a dynamic playout buffer for a disparate livemedia output stream by the DACIS 103 of FIG. 1B, in accordance with anexemplary embodiment of the disclosure.

At 602, a first programming schedule, such as the first programmingschedule 111, may be published that references at least one or morepre-encoded media assets and/or one or more live input streams. Inaccordance with an embodiment, the PEM 115 of the DACIS 103 may beconfigured to publish the first programming schedule 111 that referencesat least one or more pre-encoded media assets and/or one or more liveinput streams. Thus, the PEM 115 of the DACIS 103 may publish the firstprogramming schedule 111 referencing at least one live input stream or apre-encoded asset as a source to be used in at least a first disparatelive media output stream. In accordance with an embodiment, the one ormore live input streams may comprise pre-encoded media assets. Inaccordance with another embodiment, the one or more live input streamsmay comprise singularly encoded live input streams. Various mediacontainer formats of the live input streams and/or pre-encoded mediaassets may include, but are not limited to, transport stream (TS),fragmented MP4 (fMP4), Common Media Application Format (CMAF) and thelike.

In accordance with an embodiment, the published first programmingschedule 111 may comprise one or more playout buffer features enabledvia one or more constraints and rights. Each playout buffer feature ofthe one or more playout buffer features may be associated with acorresponding number of media segments that represents the one or morepre-encoded media assets and/or the one or more live input streams. Aplayout buffer may correspond to a specific number of media segmentsreferenced in the first disparate live media output stream manifest. Theplayout buffer may represent a maximum duration of time based on atarget duration per media segment.

In accordance with various embodiments, a first playout buffer featureof the one or more playout buffer features may correspond to a minimumplayout buffer size. The minimum playout buffer size may indicate aminimum number of media segments that represents the one or morepre-encoded media assets and/or the one or more live input streams, asdefined in the first programming schedule 111. A second playout bufferfeature of the one or more playout buffer features may correspond to amaximum playout buffer size. The maximum playout buffer size mayindicate a maximum number of media segments that represents the one ormore pre-encoded media assets and/or the one or more live input streams,as defined in the first programming schedule 111. A third playout bufferfeature of the one or more playout buffer features may correspond to adefault playout buffer size. The default playout buffer size mayindicate a pre-specified number of media segments that represents theone or more pre-encoded media assets and/or the one or more live inputstreams, as defined in the first programming schedule 111.

At 604, a fourth playout buffer feature may be determined based on areference to the repository of schedules, rights, and preferencesdatabase 144 or a third-party database by the first programming schedule111. In accordance with an embodiment, the PEM 115 of the DACIS 103 maybe configured to determine the fourth playout buffer feature based on areference to the repository of schedules, rights, and preferencesdatabase 144 or a third-party database by the first programming schedule111.

In accordance with an embodiment, the fourth playout buffer feature ofthe one or more playout buffer features may correspond to an alteredplayout buffer size. The altered playout buffer size may indicate analtered number of media segments that represents the one or morepre-encoded media assets and/or the one or more live input streams, asdefined in the first programming schedule 111.

At 606, a request may be received that comprises at least a streamidentifier and at least an additional parameter. In accordance with anembodiment, the stream publishing engine 114 in the DACIS 103 may beconfigured to receive the request that comprises at least a streamidentifier and at least an additional parameter. In accordance with anembodiment, the request may be generated by a client device, for examplethe first client device, such as client device 132 a, for the generationor retrieval of the first disparate media output stream. In accordancewith another embodiment, the request may be generated by an automatedservice for the generation or retrieval of the first disparate mediaoutput stream. In accordance with another embodiment, the request may begenerated by the client device and the automated service for thegeneration or retrieval of the first disparate media output stream.

In accordance with an embodiment, the additional parameter may include auser identifier and an altered live window duration flag. The useridentifier may correspond to a user associated with a correspondingclient device, such as the client device 132 a, at which the request isgenerated. The user identifier parameter may enable the streampublishing engine 114 to publish unique-to-client first disparate mediaoutput stream manifest leveraging the different indexes created by theindexing and storage system 116 from programming content (such as, liveinput streams and pre-encoded media assets), and non-programming content(such as advertisements) based on a defined per-client schedule, such asthe first programming schedule 111. The altered live window durationflag may correspond to a marker that may indicate that a permissibleplayout buffer duration may be retrieved from the repository ofschedules, rights, and preferences database 144 for the one or moremedia segments.

In accordance with another embodiment, the additional parameter mayinclude a desired live window duration. The desired live window durationmay correspond to a playout buffer duration that may be specified by theuser provided that the desired live window duration does not exceed themaximum playout buffer duration. In case the desired live windowduration exceeds the maximum playout buffer duration, the streampublishing engine 114 may set the playout buffer duration to the maximumplayout buffer duration, as defined in the first programming schedule111.

At 608, the indexing and storage system 116 may be queried based on thereceived request. In accordance with an embodiment, the streampublishing engine 114 in the DACIS 103 may be configured to query theindexing and storage system 116 based on the received request. The querymay comprise the stream identifier of the first disparate media outputstream.

At 610, the first programming schedule 111, the manifest data and theindexed metadata associated with the query may be determined. Inaccordance with an embodiment, the stream publishing engine 114 in theDACIS 103 may be configured to determine the first programming schedule111, the manifest data and the indexed metadata associated with thequery from the indexing and storage system 116. The indexing and storagesystem 116 may be configured to retrieve the first programming schedule111, the manifest data and the indexed metadata associated with thequery and respond back to the stream publishing engine 114 in the DACIS103.

In accordance with an embodiment, the manifest data and the indexedmetadata may correspond to the one or more media segments associatedwith the stream identifier to be inserted to the first disparate livemedia output stream manifest in accordance with the first programmingschedule 111, the playout buffer feature from the one or more playoutbuffer features, and at least the additional parameter.

In accordance with an embodiment, the indexing and storage system 116 ofthe DACIS 103 may be configured to record content of manifest data thatmay correspond to the one or more media segments associated with thestream identifier. The one or more media segments may further correspondto one or both of the one or more pre-encoded media assets and/or theone or more live input streams, including any variants defined in amaster manifest. The manifest data may correspond to one or both of anencoded live input stream and a pre-encoded media asset associated withthe stream identifier. The manifest data may define at least anassociated media content, one or more programming indicators (such asSCTE messages), timing metadata, one or more media content identifiers,and one or more contextual event identifiers. The timing metadata maycorrespond to the playback position in the published first programmingschedule 111.

In accordance with an embodiment, the indexing and storage system 116 ofthe DACIS 103 may be further configured to process the manifest data tocreate the indexed metadata. The indexed metadata may define one or moreprogram indicators (such as program start/end) and calculated durations,a program identification (that correspond to a programming content thatis currently playing), non-programming content indicators (such as Adbreak start/end) and calculated durations, a non-programming contentidentification (that correspond to Ads that are currently playing), andone or more event markers (such as blackout notifications).

In accordance with an embodiment, the indexing and storage system 116 ofthe DACIS 103 may be further configured to maintain the manifest dataand the indexed metadata to encompass a time-range specified in thepublished first programming schedule 111. For example, the indexing andstorage system 116 may keep 24 hours of indexed metadata despite thelive input stream being published in 5 minute increments.

At 612, it may be validated that the one or more media segmentsassociated with the stream identifier are eligible for a playout. Inaccordance with an embodiment, the stream publishing engine 114 in theDACIS 103 may be configured to validate that the one or more mediasegments associated with the stream identifier are eligible for theplayout. In an embodiment, the stream publishing engine 114 fails tovalidate that the one or more media segments associated with the streamidentifier are eligible for the playout and the control passes to 614.In another embodiment, the stream publishing engine 114 validates thatthe one or more media segments associated with the stream identifier areeligible for the playout and the control passes to 616.

At 614, an error notification may be generated when the one or moremedia segments associated with the stream identifier are ineligible forthe playout. In accordance with an embodiment, the stream publishingengine 114 in the DACIS 103 may be configured to generate the errornotification when the one or more media segments associated with thestream identifier are ineligible for the playout. For example, if theone or more media segments are not eligible, the stream publishingengine 114 may return an unauthorized error to the first client device,such as client device 132 a.

At 616, it may be validated that the one or more media segmentsassociated with the stream identifier are eligible in accordance withthe fourth playout buffer feature enabled via the one or moreconstraints and rights. In accordance with an embodiment, the streampublishing engine 114 in the DACIS 103 may be configured to validatethat the one or more media segments associated with the streamidentifier are eligible in accordance with the fourth playout bufferfeature enabled via the one or more constraints and rights. In anembodiment, the stream publishing engine 114 in the DACIS 103 may failto validate that the one or more media segments associated with thestream identifier are eligible in accordance with the fourth playoutbuffer feature enabled via the one or more constraints and rights, andthe control passes to step 618. In another embodiment, the streampublishing engine 114 in the DACIS 103 may validate that the one or moremedia segments associated with the stream identifier are eligible inaccordance with the fourth playout buffer feature enabled via the one ormore constraints and rights and the control passes to step 620.

At 618, a default playout buffer duration for the one or more mediasegments may be set when the one or more media segments associated withthe stream identifier are ineligible in accordance with the fourthplayout buffer feature. In accordance with an embodiment, the streampublishing engine 114 in the DACIS 103 may be configured to set thedefault playout buffer duration for the one or more media segments whenthe one or more media segments associated with the stream identifier areineligible in accordance with the fourth playout buffer feature. In suchan embodiment, the default playout buffer duration is defined in thefirst programming schedule 111. Once the default playout buffer durationis set, control passes to 636 for insertion of the manifest data andindexed metadata of one or more media segments associated with thestream identifier to the first disparate live media output streammanifest in accordance with the default playout buffer duration.

At 620, the additional parameter may be checked. In accordance with anembodiment, the stream publishing engine 114 in the DACIS 103 may beconfigured to check for the additional parameter. In an embodiment, whenthe additional parameter comprises both of the user identifier and thealtered playout buffer duration flag, control passes to 622. In anotherembodiment, when the additional parameter comprises desired playoutbuffer duration, control passes to 628. In another embodiment, when theadditional parameter comprises none of the desired playout bufferduration, and the user identifier and an altered playout buffer durationflag as well, control passes to 634.

At 622, the repository of schedules, rights, and preferences database144 may be queried based on the user identifier when the one or moremedia segments associated with the stream identifier are eligible inaccordance with the fourth playout buffer feature and at least theadditional parameter comprises both of the user identifier and thealtered playout buffer duration flag. In accordance with an embodiment,based the stream publishing engine 114 in the DACIS 103 may beconfigured to query the repository of schedules, rights, and preferencesdatabase 144 based on the user identifier when the one or more mediasegments associated with the stream identifier are eligible inaccordance with the fourth playout buffer feature and at least theadditional parameter comprises both of the user identifier and thealtered playout buffer duration flag. The repository of schedules,rights, and preferences database 144 may be configured to determine apermissible playout buffer duration associated with the user identifierand return the permissible playout buffer duration to the streampublishing engine 114.

At 624, the permissible playout buffer duration for the one or moremedia segments may be received based on the query. In accordance with anembodiment, the stream publishing engine 114 in the DACIS 103 may beconfigured to receive the permissible playout buffer duration from therepository of schedules, rights, and preferences database 144 for theone or more media segments based on the query.

At 626, the playout buffer duration for the one or more media segmentsbased on the received permissible playout buffer duration may be set. Inaccordance with an embodiment, the stream publishing engine 114 in theDACIS 103 may be configured to set the playout buffer duration for theone or more media segments based on the received permissible playoutbuffer duration. In other words, if eligible for the playout and therequest includes both of the user identifier and the altered playoutbuffer duration flag, the stream publishing engine 114 may set theplayout buffer duration according to the received permissible playoutbuffer duration. Control passes to 636 for insertion of the manifestdata and indexed metadata of one or more media segments associated withthe stream identifier to the first disparate live media output streammanifest in accordance with the playout buffer duration according to thereceived permissible playout buffer duration.

At 628, the playout buffer duration for the one or more media segmentsmay be set based on the desired playout buffer duration when the one ormore media segments associated with the stream identifier are eligiblein accordance with the fourth playout buffer feature and at least theadditional parameter comprises a desired playout buffer duration for theone or more media segments associated with the stream identifier. Inaccordance with an embodiment, the stream publishing engine 114 in theDACIS 103 may be configured to set the playout buffer duration for theone or more media segments based on the desired playout buffer durationwhen the one or more media segments associated with the streamidentifier are eligible in accordance with the fourth playout bufferfeature and at least the additional parameter comprises a desiredplayout buffer duration for the one or more media segments associatedwith the stream identifier. In other words, if eligible and requestincludes the desired live window duration, the stream publishing engine114 may set the playout buffer duration according to value dictated bydesired live window duration.

At 630, it may be checked if the desired playout buffer duration exceedsthe maximum playout buffer duration as defined in the first programmingschedule 111. In accordance with an embodiment, the stream publishingengine 114 in the DACIS 103 may be configured to check if the desiredplayout buffer duration exceeds the maximum playout buffer duration asdefined in the first programming schedule 111. In an embodiment, whenthe desired playout buffer duration exceeds the maximum playout bufferduration as defined in the first programming schedule 111, controlpasses to 632. In another embodiment, when the desired playout bufferduration does not exceed the maximum playout buffer duration as definedin the first programming schedule 111, control passes to 636 forinsertion of manifest data and indexed metadata of one or more mediasegments associated with the stream identifier to the first disparatelive media output stream manifest in accordance with the playout bufferduration based on the desired playout buffer duration.

At 632, playout buffer duration for the one or more media segments maybe set in accordance with the second playout buffer feature when thedesired playout buffer duration exceeds the maximum playout bufferduration as defined in the first programming schedule 111. In accordancewith an embodiment, the stream publishing engine 114 in the DACIS 103may be configured to set the playout buffer duration for the one or moremedia segments in accordance with the second playout buffer feature whenthe desired playout buffer duration exceeds the maximum playout bufferduration as defined in the first programming schedule 111. Controlpasses to 636 for insertion of manifest data and indexed metadata of oneor more media segments associated with the stream identifier to thefirst disparate live media output stream manifest in accordance with thesecond playout buffer feature.

At 634, the default playout buffer duration may be set for the one ormore media segments as defined in the first programming schedule 111when the one or more media segments associated with the streamidentifier are eligible for the playout and the at least the additionalparameter does not comprise the altered playout buffer duration flag orthe desired playout buffer duration. In accordance with an embodiment,the stream publishing engine 114 in the DACIS 103 may be configured toset the default playout buffer duration for the one or more mediasegments as defined in the first programming schedule 111 when the oneor more media segments associated with the stream identifier areeligible for the playout and the at least the additional parameter doesnot comprise the altered playout buffer duration flag or the desiredplayout buffer duration. In other words, if eligible and request doesnot include the altered live window duration flag or the desired livewindow duration, the stream publishing engine 114 may use default livewindow duration defined in the first programming schedule 111. Controlpasses to 636 for insertion of manifest data and indexed metadata of oneor more media segments associated with the stream identifier to thefirst disparate live media output stream manifest in accordance with thedefault live window duration.

At 636, manifest data and indexed metadata of one or more media segmentsassociated with the stream identifier may be inserted to the firstdisparate live media output stream manifest in accordance with theplayout buffer feature from the one or more playout buffer features andat least the additional parameter. In accordance with an embodiment, thestream publishing engine 114 in the DACIS 103 may be configured toinsert the manifest data and indexed metadata of one or more mediasegments associated with the stream identifier to the first disparatelive media output stream manifest in accordance with the playout bufferfeature from the one or more playout buffer features and at least theadditional parameter. As received from steps 618, 626, 630, 632, and634, the playout buffer feature and the additional parameter maycorrespond to different embodiments in accordance with which the playoutbuffer duration is set.

In accordance with one embodiment, the manifest data and indexedmetadata of one or more media segments associated with the streamidentifier that may be inserted to the first disparate live media outputstream manifest in accordance with the default playout buffer durationfor the one or more media segments, as set in step 618.

In accordance with another embodiment, the manifest data and indexedmetadata of one or more media segments associated with the streamidentifier that may be inserted to the first disparate live media outputstream manifest in accordance with the playout buffer duration for oneor more media segments based on received permissible playout bufferduration, as set in step 626.

In accordance with another embodiment, the manifest data and indexedmetadata of one or more media segments associated with the streamidentifier that may be inserted to the first disparate live media outputstream manifest in accordance with the playout buffer duration for oneor more media segments based on desired playout buffer duration, as setin step 630.

In accordance with another embodiment, the manifest data and indexedmetadata of one or more media segments associated with the streamidentifier that may be inserted to the first disparate live media outputstream manifest in accordance with the playout buffer duration for oneor more media segments in accordance with second playout buffer feature,as set in step 632.

In accordance with another embodiment, the manifest data and indexedmetadata of one or more media segments associated with the streamidentifier that may be inserted to the first disparate live media outputstream manifest in accordance with the default playout buffer durationfor one or more media segments as defined in first programming schedule111, as set in step 634.

At 636, a first disparate live media output stream may be generatedbased on the insertion of the manifest data and indexed metadata to thefirst disparate live media output stream manifest. In accordance with anembodiment, the stream publishing engine 114 in the DACIS 103 may beconfigured to generate the first disparate live media output streambased on the insertion of the manifest data and indexed metadata to thefirst disparate live media output stream manifest.

The stream publishing engine 114 may generate the first disparate livemedia output stream manifest based on one of a pre-defined conversionmodes. The pre-defined conversion modes may correspond to pre-encodedmedia assets to live stream mode, pre-encoded media assets to livestream mode with scalable architecture, a live stream to live streammode, and a mixed mode corresponding to switching between pre-encodedmedia assets and live streams.

At 638, the generated first disparate live media output stream may beplayed out. In accordance with an embodiment, the stream publishingengine 114 in the DACIS 103 may be configured to playout the generatedfirst disparate live media output stream. In an embodiment, the firstdisparate live media output stream manifest continues the insertion ofthe manifest data and indexed metadata of the one or more media segmentsuntil a total number of the one or more media segments reaches thedesired playout buffer duration. In another embodiment, the firstdisparate live media output stream manifest maintains the playout bufferduration based on removal of the manifest data and indexed metadata ofan oldest media segment for each insertion of the manifest data andindexed metadata of a new media segment when the desired playout bufferduration is reached.

Various embodiments of the disclosure comprise the media packaging anddistribution system 102 that may be configured to publish disparate livemedia output streams to be viewed on a plurality of consumer devices(such as the consumer devices 110 a, . . . , 110 n) based on userselection. The media packaging and distribution system 102 may comprise,for example, the DACIS 103, the CDS 105, the CPDS 107, the streampublishing engine 114, PEM 115, indexing and storage system 116, thestream selection service 142, and the repository of schedules, rights,and user preferences database 144. In accordance with an embodiment, oneor more processors in the DACIS 103 may be configured to receive a firstmanifest request, comprising one or more parameters, from a first clientdevice, such as client device 132 a. The one or more processors in theDACIS 103 may be further configured to determine a first additionalcontent comprising a customized first programming content and a targetedfirst non-programming content for the first client device based on theone or more parameters and associated indexed metadata retrieved basedon the one or more parameters. The one or more processors in the DACIS103 may be further configured to generate the first programming schedule111, for the first client device based on selected one or more liveinput stream and/or the one or more pre-encoded media assets, theassociated indexed metadata, and the determined first additionalcontent. The one or more processors in the DACIS 103 may be furtherconfigured to select one or more live input stream manifests and/or oneor more pre-encoded media asset manifests published in the contentdelivery system 130 and associated indexed metadata based on the one ormore parameters. The one or more processors in the DACIS 103 may befurther configured to publish a first disparate live media output streammanifest for the first client device based on insertion of the selectedone or more live input stream manifests and/or the one or morepre-encoded media asset manifests, the associated indexed metadata, andthe determined first additional content in accordance with the firstprogramming schedule 111, generated for the first client device.

In accordance with an embodiment, the one or more processors in theDACIS 103 may be further configured to index a plurality of mediasegments indicated by the one or more pre-encoded media asset manifestsand the one or more live input stream manifests, the associated indexedmetadata, the targeted first non-programming content, and the customizedfirst programming content based on the first programming schedule 111generated for the first client. In accordance with an embodiment, theone or more processors in the DACIS 103 may be further configured toinsert the first additional content at one or more content placementopportunities indicated in the first disparate live media output streammanifest based on the first programming schedule 111 generated for thefirst client device. The one or more content placement opportunities maybe defined by the metadata associated with the one or more live inputstreams corresponding to the one or more live input stream manifestsand/or one or more pre-encoded media assets corresponding to the one ormore pre-encoded media asset manifests. The insertion of the targetedfirst non-programming content and the customized first programmingcontent in real time, the associated indexed metadata and/or the one ormore content placement opportunities may include programming contentindicators, non-programming content indicators, graphical treatmentindicators, and interactive content indicators.

In accordance with an embodiment, the insertion of the customized firstprogramming content, in an instance in which the generated firstdisparate live media output stream manifest corresponds to a disparatelive media output stream, a first set of processors in the DACIS 103 maybe further configured to receive universal resource locators and/oridentifiers referencing records for the selected one or more live inputstreams and/or the one or more pre-encoded media assets from the CPDS107. The associated indexed metadata and/or one or more contentplacement opportunities may include programming content indicators,non-programming content indicators, graphical treatment indicators, andinteractive content indicators. The programming content indicators maycomprise a plurality of categories for the customized first programmingcontent.

In accordance with an embodiment, the first set of processors in theDACIS 103 may be further configured to transmit a request to the CDS 105for determining the customized first programming content from a contentpackage and distribution system for matching one or more personalizationparameters. The one or more personalization parameters may include userpreferences and identifiers from the first manifest request or retrievedfrom the repository of schedules, rights, and user preferences database144, and time constraints. The time constraints may be determined basedon user preferences retrieved from the repository of schedules, rights,and user preferences database 144, a range defined in the first manifestrequest, and schedule tolerances defined in the repository of schedules,rights, and user preferences database 144, client device preferences oridentifiers from the first manifest request or retrieved from therepository of schedules, rights, and user preferences database 144,geolocation information from the first manifest request or retrievedfrom the repository of schedules, rights, and user preferences database144, and/or a content recommendation engine.

In accordance with an embodiment, the one or more parameters maycomprise universal resource locators and/or identifiers referencingrecords for one or more live input streams or one or more pre-encodedmedia assets in the CPDS 107, a plurality of client-specific parameters,and a plurality of client-specified attributes derived from a userinteraction with the first client device. The plurality ofclient-specific parameters may comprise user preferences andidentifiers, client device preferences and identifiers, and one or morerules governed by geolocation data and current position of playback of afirst disparate live media output stream at the first client device. Inaccordance with an embodiment, for the insertion of the targeted firstnon-programming content, the plurality of client-specified attributesmay comprise the user interaction with interactive content in thecustomized first programming content and the targeted firstnon-programming content, and a preference for a type and/or category ofthe targeted first non-programming content and/or the customized firstprogramming content. The user interaction with the interactive contentcomprises a selection to exclude the targeted first non-programmingcontent and/or the customized first programming content, a selection toinclude a subset of the targeted first non-programming content and/orthe customized first programming content, and a selection to include allof the targeted first non-programming content and/or the customizedfirst programming content within one or more specified non-programmingcontent locations. The targeted first non-programming content maycomprise personalized advertisements including video advertisements,graphical treatment, cue points, and the interactive content comprisinga set of interactive elements for the targeted first non-programmingcontent. The customized first programming content may comprisepersonalized non-advertising content including promotional content, ashort-form content, and an alternate additional content for replacementof at least a portion of a first disparate live media output streamgenerated for the first client.

In accordance with an embodiment, the one or more processors in theDACIS 103 may be further configured to transmit the published firstdisparate live media output stream manifest to a media player of thefirst client device for a playback of a first disparate live mediaoutput stream. The media player, during playback of the first disparatelive media output stream at the first client device, may present one ormore decision points defined by the interactive content to initiate auser interaction at the first client device. At the one or more decisionpoints, the user interaction may correspond to one of a desiredselection corresponding to the user interaction with one or moreinteractive elements, or a default selection corresponding tonon-interaction of a user with the customized first programming contentand/or the targeted first non-programming content in the first disparatelive media output stream played back by the media player. The desiredselection or the default selection may be transmitted to an externalstorage system that is the repository of schedules, rights, and userpreferences database 144. At the one or more decision points, the one ormore interactive elements may be configured to exclude the targetedfirst non-programming content or the customized first programmingcontent and be replaced by default content, select alternate customizedfirst programming content, select a subsequent second programmingcontent, approve or disapprove selected customized first programmingcontent, exclude subsequent second non-programming content for aremaining portion of the first disparate live media output stream playedback by the media player, select one or more targeted firstnon-programming content of a specific category, or view some or all ofthe targeted first non-programming content immediately to avoid some orall of the targeted first non-programming content for the remainingportion of the first disparate live media output stream played back bythe media player.

In accordance with an embodiment, the one or more processors in theDACIS 103 may be further configured to modify a remaining portion of thefirst programming schedule 111 that generates first disparate live mediaoutput stream corresponding to the first manifest request generated bythe first client device based on the user interaction with theinteractive content. A first set of processors in the DACIS 103 may beconfigured to receive the first manifest request from a second set ofprocessors in the DACIS 103, select, based on the received firstmanifest request, one or more live input streams and/or one or morepre-encoded media assets based on the one or more parameters andadditional parameters retrieved from the repository of schedules,rights, and user preferences database 144, and transmit universalresource locators and/or identifiers referencing records for theselected one or more live input streams and/or the one or morepre-encoded media assets to the second set of processors in the DACIS103.

In accordance with an embodiment, the second set of processors in theDACIS 103 may be further configured to retrieve the indexed metadataassociated with the selected one or more live input streams and/or theone or more pre-encoded media assets from the CPDS 107. The associatedindexed metadata may define one or more content placement opportunitieswithin the selected one or more live input streams and/or the one ormore pre-encoded media assets. The customized first programming contentand the targeted first non-programming content may be identified as thefirst additional content to be scheduled at the one or more contentplacement opportunities based on the one or more parameters in thereceived first manifest request and the associated indexed metadata,wherein the generated first programming schedule 111 excludes the firstadditional content or includes the first additional content completelyor partially.

In accordance with an embodiment, a third set of processors in the DACIS103 may be further configured to insert, based on the generated firstprogramming schedule 111, the identified customized first programmingcontent and the targeted first non-programming content into the firstdisparate live media output stream manifest in accordance with the oneor more content placement opportunities defined in the associatedindexed metadata and one or more rules and conditions defined in therepository of schedules, rights, and user preferences database 144. Theidentification of the targeted first non-programming content may bebased on execution of a non-programming content service based on rulesand conditions defined in additional parameters of the repository ofschedules, rights, and user preferences database 144, and the one ormore parameters defined in the first manifest request. Theidentification of the customized first programming content may be basedon execution of the CDS 105 based on the rules and conditions defined inthe additional parameters of the repository of schedules, rights, anduser preferences database 144. In accordance with an embodiment, thefirst programming schedule 111 may define locations and types of one ormore decision points defined by one or more content placementopportunities in the indexed metadata. In an instance when one or morepre-encoded media assets are being scheduled and the one or moredecision points defined by the one or more content placementopportunities are to be inserted in the first programming schedule 111,the first programming schedule 111 may be configured to control the oneor more pre-encoded media asset manifests to be published as the firstdisparate live media output stream manifest.

In accordance with an embodiment, a conversion of one or morepre-encoded media assets into a first disparate live media output streamfacilitates one or more subsequent modifications on the first disparatelive media output stream. The one or more subsequent modifications maycorrespond to a user selection, a user preference, a change in the firstprogramming schedule 111, or a time or geolocation-based rule.

In accordance with an embodiment, the first set of processors in theDACIS 103 may be further configured to transmit universal resourcelocators and/or identifiers referencing records for the selected one ormore live input streams and/or the one or more pre-encoded media assetsto the second set of processors. In an absence of one or more live inputstreams, the first set of processors may be configured to select apre-encoded asset indicated in the first manifest request to continueplayback as the first disparate live media output stream. The second setof processors may be configured to select a second disparate live mediaoutput stream according to accessibility of the first disparate livemedia output stream. The first disparate live media output stream is notupdated and/or the first disparate live media output stream has mediaand/or a manifest that is incompatible with a client request. The secondset of processors may be further configured to select the seconddisparate live media output stream according to rules provided by astream owner/operator and user preferences defined in the repository ofschedules, rights, and user preferences database 144.

In accordance with an embodiment, the one or more processors in theDACIS 103 may be further configured to transition from the firstadditional content to an alternate additional content based on one ormore transition parameters. The one or more transition parameters maycomprise one or more parameters from the first manifest request, currentstate of the first disparate live media output stream manifestdetermined based on accessibility, regular update, and suitableencoding, digital rights management, and compatibility with the firstclient device, rules provided by a stream owner operator, and userpreferences defined in the repository of schedules, rights, and userpreferences database 144.

In accordance with an embodiment, the one or more processors in theDACIS 103 may be further configured to retrieve alternate metadata forthe alternate additional content from the CPDS 107. The alternatemetadata may indicate a location to transition from the first additionalcontent to the alternate additional content. The one or more processorsmay be further configured to determine placement of the alternateadditional content within the first disparate live media output streammanifest based on the associated indexed metadata and the alternatemetadata. The one or more processors may be further configured togenerate the alternate programming schedule 113, for the first clientdevice based on the alternate additional content and the alternatemetadata, and transmit the generated alternate programming schedule tothe first set of processors. The first set of processors may beconfigured to generate a final disparate live output stream manifest forthe first client device. In accordance with an embodiment, anotherconversion of the first disparate live media output stream into the oneor more pre-encoded media assets facilitates download of the one or morepre-encoded media assets at the first client device and mitigatesdependency on the system for playback of remaining portion. Inaccordance with an embodiment, the one or more processors in the DACIS103 may be further configured to receive a request from the first clientdevice, wherein the request comprises the one or more parameters. Theone or more processors in the DACIS 103 may be further configured todetermine alternate additional content for inclusion in the firstdisparate live media output stream manifest or replacement of the firstadditional content in the first disparate live media output streammanifest based on the one or more parameters. The one or more processorsin the DACIS 103 may be further configured to modify the firstprogramming schedule 111 to generate an alternate programming schedulefor the first client device based on the alternate additional contentand associated metadata. The one or more processors in the DACIS 103 maybe further configured to transmit the generated alternate programmingschedule to a second set of processors, wherein the second set ofprocessors is configured to generate a final disparate live outputstream manifest for the first client device.

In accordance with an embodiment, the one or more processors in theDACIS 103 may be further configured to revoke the first disparate livemedia output stream manifest published for the first client device basedon an identifier primitive associated with the first disparate livemedia output stream of the first client device in an instance in which amedia player of the first client device is determined to be aplagiarized media player. The first disparate live media output streammay include at least one unique identifier inserted by the one or moreprocessors in the DACIS 103.

In accordance with various embodiments, the first disparate live mediaoutput stream manifest for the first client device may be generatedbased on one of a pre-defined conversion modes. The pre-definedconversion modes may correspond to pre-encoded media assets to livestream mode, pre-encoded media assets to live stream mode with scalablearchitecture, a live stream to live stream mode, and a mixed modecorresponding to switching between pre-encoded media assets and livestreams.

In accordance with an embodiment, one or more processors in the PEM 115may be configured to receive a first manifest request, comprising one ormore parameters, from the first client device. Further, the receivedfirst manifest request may be transmitted to a first set of processorsin the stream selection service 142. The first set of processors may beconfigured to select, based on the received first manifest request, oneor more live input streams and/or one or more pre-encoded media assetsbased on the one or more parameters and additional parameters retrievedfrom the repository of schedules, rights, and user preferences database144. The one or more processors in the PEM 115 may be configured toreceive universal resource locators and/or identifiers referencingrecords for the selected one or more live input streams and/or the oneor more pre-encoded media assets from the first set of processors. Theone or more processors in the PEM 115 may be configured to retrieveindexed metadata associated with the selected one or more live inputstreams and/or the one or more pre-encoded media assets from a contentpackaging and distribution system, wherein the indexed metadata definesone or more content placement opportunities within the selected one ormore live input streams and/or the one or more pre-encoded media assets.The one or more processors in the PEM 115 may be further configured toidentify a customized first programming content and a targeted firstnon-programming content as a first additional content to be scheduled inthe one or more content placement opportunities based on the one or moreparameters in the received first manifest and the associated indexedmetadata. The one or more processors in the PEM 115 may be furtherconfigured to generate the first programming schedule 111 for the firstclient device based on the associated indexed metadata, the firstadditional content and the one or more live input streams and/or one ormore pre-encoded media assets.

Various embodiments of the disclosure comprise one or more processors inthe media packaging and distribution system 102 that may be configuredto provide a dynamic playout buffer for disparate live media outputstream to be viewed on a plurality of consumer devices (such as theconsumer devices 110 a, . . . , 110 n). The media packaging anddistribution system 102 may comprise, for example, the DACIS 103, thestream publishing engine 114, the PEM 115, the indexing and storagesystem 116, and the repository of schedules, rights, and userpreferences database 144. The one or more processors in the DACIS 103may be configured to publish the first programming schedule 111 that mayreference at least one or more pre-encoded media assets and/or one ormore live input streams. The published first programming schedule 111may comprise one or more playout buffer features enabled via one or moreconstraints and rights. Each playout buffer feature of the one or moreplayout buffer features may be associated with a corresponding number ofmedia segments that represents the one or more pre-encoded media assetsand/or the one or more live input streams. The one or more processors inthe DACIS 103 may be further configured to receive a request thatcomprises at least a stream identifier and at least an additionalparameter. The one or more processors in the DACIS 103 may be furtherconfigured to insert manifest data and indexed metadata of one or moremedia segments associated with the stream identifier to a firstdisparate live media output stream manifest in accordance with a playoutbuffer feature from the one or more playout buffer features and at leastthe additional parameter. The one or more processors in the DACIS 103may be further configured to generate a first disparate live mediaoutput stream based on the insertion of the manifest data and indexedmetadata to the first disparate live media output stream manifest.

In accordance with various embodiments, a first playout buffer featureof the one or more playout buffer features may correspond to a minimumplayout buffer size. The minimum playout buffer size may indicate aminimum number of media segments that represents the one or morepre-encoded media assets and/or the one or more live input streams, asdefined in the first programming schedule 111. A second playout bufferfeature of the one or more playout buffer features may correspond to amaximum playout buffer size. The maximum playout buffer size mayindicate a maximum number of media segments that represents the one ormore pre-encoded media assets and/or the one or more live input streams,as defined in the first programming schedule 111. A third playout bufferfeature of the one or more playout buffer features may correspond to adefault playout buffer size. The default playout buffer size mayindicate a pre-specified number of media segments that represents theone or more pre-encoded media assets and/or the one or more live inputstreams, as defined in the first programming schedule 111. A fourthplayout buffer feature of the one or more playout buffer features maycorrespond to an altered playout buffer size. The altered playout buffersize may indicate an altered number of media segments that representsthe one or more pre-encoded media assets and/or the one or more liveinput streams, as defined in the first programming schedule 111. Inaccordance with an embodiment, the one or more processors in the DACIS103 may be configured to determine the fourth playout buffer featurebased on a reference to a repository of schedules, rights, andpreferences database 144 or a third-party database by the firstprogramming schedule 111. The request may be generated by at least oneof a client device or an automated service for the generation of thefirst disparate media output stream.

In accordance with an embodiment, the one or more processors in theDACIS 103 may be further configured to query the indexing and storagesystem 116 based on the received request. The query may comprise thestream identifier. In accordance with an embodiment, the one or moreprocessors in the DACIS 103 may be further configured to determine thefirst programming schedule 111, the manifest data and the indexedmetadata associated with the query. The manifest data and the indexedmetadata may correspond to the one or more media segments associatedwith the stream identifier to be inserted to the first disparate livemedia output stream manifest in accordance with the first programmingschedule 111, the playout buffer feature from the one or more playoutbuffer features, and at least the additional parameter.

In accordance with an embodiment, the one or more processors in theDACIS 103 may be further configured to validate that the one or moremedia segments associated with the stream identifier are eligible for aplayout. Accordingly, the one or more processors in the DACIS 103 may befurther configured to generate an error notification when the one ormore media segments associated with the stream identifier are ineligiblefor the playout.

In accordance with an embodiment, the one or more processors in theDACIS 103 may be further configured to validate that the one or moremedia segments associated with the stream identifier are eligible inaccordance with the fourth playout buffer feature enabled via the one ormore constraints and rights. In accordance with an embodiment, the oneor more processors in the DACIS 103 may be further configured to set adefault playout buffer duration for the one or more media segments whenthe one or more media segments associated with the stream identifier areineligible in accordance with the fourth playout buffer feature. Thedefault playout buffer duration may be defined in the first programmingschedule 111.

In accordance with an embodiment, when the one or more media segmentsassociated with the stream identifier are eligible in accordance withthe fourth playout buffer feature and at least the additional parametercomprises both of a user identifier and an altered playout bufferduration flag, the one or more processors in the DACIS 103 may befurther configured to query the repository of schedules, rights, andpreferences database 144 based on the user identifier. In accordancewith an embodiment, the one or more processors in the DACIS 103 may befurther configured to receive a permissible playout buffer duration forthe one or more media segments based on the query. In accordance with anembodiment, the one or more processors in the DACIS 103 may be furtherconfigured to set a playout buffer duration for the one or more mediasegments based on the received permissible playout buffer duration.

In accordance with an embodiment, when the one or more media segmentsassociated with the stream identifier are eligible in accordance withthe fourth playout buffer feature and at least the additional parametercomprises a desired playout buffer duration for the one or more mediasegments associated with the stream identifier, the one or moreprocessors in the DACIS 103 may be further configured to set a playoutbuffer duration for the one or more media segments based on the desiredplayout buffer duration. In accordance with an embodiment, the one ormore processors in the DACIS 103 may be further configured to set theplayout buffer duration for the one or more media segments in accordancewith the second playout buffer feature when the desired playout bufferduration exceeds a maximum playout buffer duration as defined in thefirst programming schedule 111.

In accordance with an embodiment, the one or more processors in theDACIS 103 may be further configured to playout the generated firstdisparate live media output stream. In an embodiment, the firstdisparate live media output stream manifest may continue the insertionof the manifest data and indexed metadata of the one or more mediasegments until a total number of the one or more media segments reachesthe desired playout buffer duration. In another embodiment, the firstdisparate live media output stream manifest may maintain the playoutbuffer duration based on removal of the manifest data and indexedmetadata of an oldest media segment for each insertion of the manifestdata and indexed metadata of a new media segment when the desiredplayout buffer duration is reached.

In accordance with an embodiment, when the one or more media segmentsassociated with the stream identifier are eligible for the playout andthe at least the additional parameter does not comprise an alteredplayout buffer duration flag or a desired playout buffer duration, theone or more processors in the DACIS 103 may be further configured to seta default playout buffer duration for the one or more media segments asdefined in the first programming schedule 111.

Various embodiments of the disclosure may provide a computer-readablemedium, such as the non-transitory computer-readable medium 506, havingstored thereon, computer implemented instruction that when executed bythe processor 504 causes the media packaging and distribution system 102to execute operations for publishing a disparate per-client live mediaoutput stream based on dynamic insertion of targeted non-programmingcontent and customized programming content. In accordance with anembodiment, the processor 504 causes the media packaging anddistribution system 102 to execute operations to receive a firstmanifest request, comprising one or more parameters, from a first clientdevice, such as client device 132 a. The processor 504 causes the mediapackaging and distribution system 102 to execute operations to determinea first additional content comprising a customized first programmingcontent and a targeted first non-programming content for the firstclient device based on the one or more parameters and associated indexedmetadata retrieved based on the one or more parameters. The processor504 causes the media packaging and distribution system 102 to executeoperations to generate the first programming schedule 111, for the firstclient device based on selected one or more live input stream and/or theone or more pre-encoded media assets, the associated indexed metadata,and the determined first additional content. The processor 504 causesthe media packaging and distribution system 102 to execute operations toselect one or more live input stream manifests and/or one or morepre-encoded media asset manifests published in the content deliverysystem 130 and associated indexed metadata based on the one or moreparameters. The processor 504 causes the media packaging anddistribution system 102 to execute operations to publish a firstdisparate live media output stream manifest for the first client devicebased on insertion of the selected one or more live input streammanifests and/or the one or more pre-encoded media asset manifests, theassociated indexed metadata, and the determined first additional contentin accordance with the first programming schedule 111, generated for thefirst client device.

Various embodiments of the disclosure may provide a computer-readablemedium, such as the non-transitory computer-readable medium 506, havingstored thereon, computer implemented instruction that when executed bythe processor 504 causes the media packaging and distribution system 102to execute operations for publishing the first programming schedule 111that references at least one or more pre-encoded media assets and/or oneor more live input streams. The published first programming schedule 111may comprise one or more playout buffer features enabled via one or moreconstraints and rights. Each playout buffer feature of the one or moreplayout buffer features may be associated with a corresponding number ofmedia segments that represents the one or more pre-encoded media assetsand/or the one or more live input streams. In accordance with anembodiment, the processor 504 causes the media packaging anddistribution system 102 to execute operations for receiving a requestthat comprises at least a stream identifier and at least an additionalparameter. In accordance with an embodiment, the processor 504 causesthe media packaging and distribution system 102 to execute operationsfor inserting manifest data and indexed metadata of one or more mediasegments associated with the stream identifier to a first disparate livemedia output stream manifest in accordance with a playout buffer featurefrom the one or more playout buffer features and at least the additionalparameter. In accordance with an embodiment, the processor 504 causesthe media packaging and distribution system 102 to execute operationsfor generating a first disparate live media output stream based on theinsertion of the manifest data and indexed metadata to the firstdisparate live media output stream manifest.

Existing systems for SSAI support live streaming and make decisions toinsert non-programing content in near real-time. However, for On-Demandstreaming, such decisions to insert non-programing content are madeupfront. Accordingly, amount of control the user can excerpt toinfluence what non-programming content is shown may get limited.Further, newer ad models are developing that rely less on interruptivevideo advertising and more on contextual based graphical treatmentadvertising within the program content. To this extent, SSAI systemshave been able to circumvent ad blockers by requesting video ads onbehalf of the client device and stitching them into the disparate livemedia output stream manifest. Typically, modern streaming protocols,that are implemented to support streaming of various live contentservices in such SSAI systems, require that a playout buffer for a livemedia output stream is definite and unchanging, so that a media playerat a client device can suitably create rules, based on which mediasegments are fetched, buffered, and played out.

To address at least the above problems, in accordance with the variousembodiments of the present disclosure, the DACIS 103 in the mediapackaging and distribution system 102 may be configured to include notshowing non-programming content that the user elected to skip or ratedpoorly in an earlier non-programming content break, or could enable theuser to skip all non-programming content because the user interactedwith an previous non-programming content or made a purchase and theadvertiser elected to sponsor the remainder of the program.

The DACIS 103 may notified about graphical treatment opportunitieswithin the content, make the necessary ad calls on behalf of the clientdevice, and provide the client device with the information needed toexecute the overlays via a secure out-of-band channel between the DACIS103 and the client device. In many cases, a channel already exists tosupport passing the program indicators, such as start and endinformation, to the client device and Video Player Ad-Serving Interface(VPAID) ads that cannot be stitched.

DACIS 103 may also provide an opportunity to leverage the 1:1 scale oftraditional SSAI systems to support custom content choices and not justtargeted advertising. For example, when a user selects to join a livestream, the CDS 105 coupled with the DACIS 103 may determine that,instead of joining the live stream for the last few minutes of aprogram, the user should instead be shown content more relevant to thenext program. For example, showing a personalized set of basketballhighlights and ads to a user who likely joined the stream to watch thebasketball game that is coming on next.

Further, the DACIS 103 may be used to provide seamless failover betweenredundant streams for large events, thus improving reliability. Whilesome client devices support primary and backup streams and are able tofail between them, many client devices do not. In such cases, the clientdevice may attempt to join the alternative stream after occurrence of anevent, such as a device failure or crash. For such clients, the DACIS103 monitors both the primary and backup stream, and if there is afailure, inserts the alternative stream into the output manifest. Thus,the media packaging and distribution system 102 provides an enhanced,intelligent, and personalized viewer experience with increased appeal inorder to retain and gain a wider audience.

The DACIS 103, the CDS 105, the CPDS 107, the stream publishing engine114, PEM 115, indexing and storage system 116, the stream selectionservice 142, and the repository of schedules, rights, and userpreferences database 144 in conjunction with each other, providesignificant productivity and efficiency improvements since the processof generating disparate live media output streams with additionalcontent is specific to each consumer device. The disparate live mediaoutput streams are simplified as the generated disparate live mediaoutput streams are independent of a requirement to re-process, that isre-encode and re-package, various live input streams for mediadistribution to the plurality of consumer devices in real time ornear-real time. Thus, the network provider now may provide live channelofferings in a cost-effective manner.

Various components, as described above in FIG. 1B, enable the mediapackaging and distribution system 102 to leverage the modern streamingprotocols, based on which the media packaging and distribution system102 generates disparate live media output streams of the live broadcastchannels with additional content and one or more decision points toinfluence the remaining disparate live media output streams. Thedisparate live media output streams may be generated based on insertionof live input streams into a generated disparate live media outputstream using pre-encoded media assets. In this regard, manifests fromthe live input streams and the pre-encoded media assets may bemanipulated and produced for distribution of the disparate live mediaoutput stream.

As the media content itself does not need to be processed beyond theinitial creation of the live input streams and pre-encoded media assetsprepared for distribution, it is extremely inexpensive to provide suchdisparate live media output streams and alternate disparate live mediaoutput stream (in case of stream failover). It may be based solely onthe cost to manipulate the manifests, which provide the instructions forthe media players in the client devices 132 a, . . . , 132 n to execute.The media packaging and distribution system 102 may also supporttargeted ad insertion and customized programming content insertion on aper client basis and may further leverage the processing power of theindividual client devices 132 a, . . . , 132 n to insert targetedchannel graphics and graphical treatment advertisements and promotions.

In accordance with the system and method for providing a dynamic playoutbuffer for disparate live media output stream, as proposed herein, uponthe initial request, the size of the playout buffer (or the live window)may be requested by the client device or specified by the firstprogramming schedule 111 and/or the repository of schedules, rights, anduser preferences database 144. The manifest data and the indexedmetadata of one or more media segments associated with the streamidentifier may be determined for each unique client device, based on acombination of business rules, a playout buffer feature and at least theadditional parameter, at the time of request. Accordingly, a firstdisparate live media output stream is tailored resulting in a dynamicplayout buffer specific for that client device. Thus, the size of theplayout buffer (or the live window) is unique per the client device, butpotentially for the same published disparate live media output streams.

As utilized herein the terms “circuits” and “circuitry” refer tophysical electronic components (for example, hardware) and any softwareand/or firmware (“code”) which may configure the hardware, be executedby the hardware, and/or otherwise be associated with the hardware. Asused herein, for example, a particular processor and memory may comprisea first “circuit” when executing first one or more lines of code and maycomprise a second “circuit” when executing second one or more lines ofcode. As utilized herein, “and/or” means any one or more of the items inthe list joined by “and/or”. As an example, “x and/or y” means anyelement of the three-element set {(x), (y), (x, y)}. As another example,“x, y, and/or z” means any element of the seven-element set {(x), (y),(z), (x, y), (x, z), (y, z), (x, y, z)}. As utilized herein, the term“exemplary” means serving as a non-limiting example, instance, orillustration. As utilized herein, the terms “e.g.,” and “for example”set off lists of one or more non-limiting examples, instances, orillustrations. As utilized herein, circuitry is “operable” to perform afunction whenever the circuitry comprises the necessary hardware and/orcode (if any is necessary) to perform the function, regardless ofwhether performance of the function is disabled, or not enabled, by someuser-configurable setting.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of embodiments ofthe disclosure. As used herein, the singular forms “a”, “an” and “the”are intended to include the plural forms as well, unless the contextclearly indicates otherwise. It will be further understood that theterms “comprises”, “comprising”, “includes” and/or “including”, whenused herein, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

Further, many embodiments are described in terms of sequences of actionsto be performed by, for example, elements of a computing device. It willbe recognized that various actions described herein can be performed byspecific circuits (e.g., application specific integrated circuits(ASICs)), by program instructions being executed by one or moreprocessors, or by a combination of both. Additionally, these sequencesof actions described herein can be considered to be embodied entirelywithin any non-transitory form of computer readable storage mediumhaving stored therein a corresponding set of computer instructions thatupon execution would cause an associated processor to perform thefunctionality described herein. Thus, the various aspects of thedisclosure may be embodied in a number of different forms, which havebeen contemplated to be within the scope of the claimed subject matter.In addition, for each of the embodiments described herein, thecorresponding form of any such embodiments may be described herein as,for example, “logic configured to” perform the described action.

Another embodiment of the disclosure may provide a non-transitorymachine and/or computer readable storage and/or media, having storedthereon, a machine code and/or a computer program having at least onecode section executable by a machine and/or a computer, thereby causingthe machine and/or computer to perform the steps as described herein forpublishing a disparate per-client live media output stream based ondynamic insertion of targeted non-programming content and customizedprogramming content.

The present disclosure may also be embedded in a computer programproduct, which comprises all the features enabling the implementation ofthe methods described herein, and which when loaded in a computer systemis able to carry out these methods. Computer program in the presentcontext means any expression, in any language, code or notation, eitherstatically or dynamically defined, of a set of instructions intended tocause a system having an information processing capability to perform aparticular function either directly or after either or both of thefollowing: a) conversion to another language, code or notation; b)reproduction in a different material form.

Further, those of skill in the art will appreciate that the variousillustrative logical blocks, modules, circuits, algorithms, and/or stepsdescribed in connection with the embodiments disclosed herein may beimplemented as electronic hardware, computer software, firmware, orcombinations thereof. To clearly illustrate this interchangeability ofhardware and software, various illustrative components, blocks, modules,circuits, and steps have been described above generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of the presentdisclosure.

The methods, sequences and/or algorithms described in connection withthe embodiments disclosed herein may be embodied directly in firmware,hardware, in a software module executed by a processor, or in acombination thereof. A software module may reside in RAM memory, flashmemory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk,physical and/or virtual disk, a removable disk, a CD-ROM, virtualizedsystem or device such as a virtual servers or container, or any otherform of storage medium known in the art. An exemplary storage medium iscommunicatively coupled to the processor (including logic/code executingin the processor) such that the processor can read information from, andwrite information to, the storage medium. In the alternative, thestorage medium may be integral to the processor.

While the present disclosure has been described with reference tocertain embodiments, it will be noted understood by, for example, thoseskilled in the art that various changes and modifications could be madeand equivalents may be substituted without departing from the scope ofthe present disclosure as defined, for example, in the appended claims.In addition, many modifications may be made to adapt a particularsituation or material to the teachings of the present disclosure withoutdeparting from its scope. The functions, steps and/or actions of themethod claims in accordance with the embodiments of the disclosuredescribed herein need not be performed in any particular order.Furthermore, although elements of the disclosure may be described orclaimed in the singular, the plural is contemplated unless limitation tothe singular is explicitly stated. Therefore, it is intended that thepresent disclosure not be limited to the particular embodimentdisclosed, but that the present disclosure will include all embodimentsfalling within the scope of the appended claims.

What is claimed is:
 1. A system, comprising: a memory for storinginstructions; and a processor for executing the instructions to performoperations, the operations comprising: receive a request that comprisesa stream identifier and an additional parameter; and generate a firstdisparate live media output stream based on an insertion of manifestdata and indexed metadata of a media segment associated with the streamidentifier to a first disparate live media output stream manifest inaccordance with a playout buffer feature of a plurality of playoutbuffer features and the additional parameter, wherein the playout bufferfeature, defined in a first programming schedule, is associated with acorresponding number of media segments representing pre-encoded mediaassets and/or live input streams referenced in the first programmingschedule.
 2. The system according to claim 1, wherein a first playoutbuffer feature from the plurality of playout buffer features correspondsto a minimum playout buffer size, wherein the minimum playout buffersize indicates a minimum number of media segments that represents thepre-encoded media assets and/or the live input streams, as defined inthe first programming schedule, wherein a second playout buffer featurefrom the plurality of playout buffer features corresponds to a maximumplayout buffer size, wherein the maximum playout buffer size indicates amaximum number of media segments that represents the pre-encoded mediaassets and/or the live input streams, as defined in the firstprogramming schedule, wherein a third playout buffer feature from theplurality of playout buffer features corresponds to a default playoutbuffer size, wherein the default playout buffer size indicates apre-specified number of media segments that represents the pre-encodedmedia assets and/or the live input streams, as defined in the firstprogramming schedule, wherein a fourth playout buffer feature from theplurality of playout buffer features corresponds to an altered playoutbuffer size, and wherein the altered playout buffer size indicates analtered number of media segments that represents the pre-encoded mediaassets and/or the live input streams, as defined in the firstprogramming schedule.
 3. The system according to claim 2, wherein theoperations further comprise: set a playout buffer duration for the mediasegments in accordance with the second playout buffer feature when adesired playout buffer duration exceeds a maximum playout bufferduration as defined in the first programming schedule.
 4. The systemaccording to claim 2, wherein the operations further comprise: determinethe fourth playout buffer feature based on a reference to a repositoryof schedules, rights, and preferences database or a third-party databaseby the first programming schedule.
 5. The system according to claim 4,wherein the operations further comprise: validate that the mediasegments associated with the stream identifier are eligible inaccordance with the fourth playout buffer feature enabled viaconstraints and rights.
 6. The system according to claim 5, wherein theoperations further comprise: set a default playout buffer duration forthe media segments when the media segments associated with the streamidentifier are ineligible in accordance with the fourth playout bufferfeature, wherein the default playout buffer duration is defined in thefirst programming schedule.
 7. The system according to claim 5, wherein,when the media segments associated with the stream identifier areeligible in accordance with the fourth playout buffer feature and theadditional parameter comprises both of a user identifier and an alteredplayout buffer duration flag, the operations further comprise: query therepository of schedules, rights, and preferences database based on theuser identifier; receive a permissible playout buffer duration for themedia segments based on the query; and set a playout buffer duration forthe media segments based on the received permissible playout bufferduration.
 8. The system according to claim 5, wherein, when the mediasegments associated with the stream identifier are eligible inaccordance with the fourth playout buffer feature and the additionalparameter comprises a desired playout buffer duration for the mediasegments associated with the stream identifier, the operations furthercomprise: set a playout buffer duration for the media segments based onthe desired playout buffer duration.
 9. The system according to claim 8,wherein the operations further comprise: playout the generated firstdisparate live media output stream, wherein the first disparate livemedia output stream manifest continues the insertion of the manifestdata and indexed metadata of the media segments until a total number ofthe media segments reaches the desired playout buffer duration.
 10. Thesystem according to claim 8, wherein the operations further comprise:playout the generated first disparate live media output stream, whereinthe first disparate live media output stream manifest maintains theplayout buffer duration based on removal of the manifest data andindexed metadata of an oldest media segment for each insertion of themanifest data and indexed metadata of a new media segment when thedesired playout buffer duration is reached.
 11. The system according toclaim 1, wherein the operations further comprise: query an indexing andstorage system based on the received request, wherein the querycomprises the stream identifier; and determine the first programmingschedule, the manifest data and the indexed metadata associated with thequery, wherein the manifest data and the indexed metadata correspond tothe media segments associated with the stream identifier to be insertedto the first disparate live media output stream manifest in accordancewith the first programming schedule, the playout buffer feature from theplurality of playout buffer features, and at least the additionalparameter.
 12. The system according to claim 1, wherein the operationsfurther comprise: validate that media segments associated with thestream identifier are eligible for a playout.
 13. The system accordingto claim 12, wherein the operations further comprise: generate an errornotification when the media segments associated with the streamidentifier are ineligible for the playout.
 14. The system according toclaim 12, wherein, when the media segments associated with the streamidentifier are eligible for the playout and the additional parameterdoes not comprise an altered playout buffer duration flag or a desiredplayout buffer duration, the operations further comprise: set a defaultplayout buffer duration for the media segments as defined in the firstprogramming schedule.
 15. The system according to claim 1, wherein theoperations comprise: publish the first programming schedule thatcomprises the plurality of playout buffer features enabled viaconstraints and rights, wherein the request is generated by at least oneof a client device or an automated service for the generation of thefirst disparate live media output stream.
 16. A method, comprising:receiving, by a processor, a request that comprises a stream identifierand an additional parameter; and generating, by the processor, a firstdisparate live media output stream based on an insertion of manifestdata and indexed metadata of a media segment associated with the streamidentifier to a first disparate live media output stream manifest inaccordance with a playout buffer feature of a plurality of playoutbuffer features and the additional parameter, wherein the playout bufferfeature, defined in a first programming schedule, is associated with acorresponding number of media segments representing pre-encoded mediaassets and/or live input streams referenced in the first programmingschedule.
 17. The method according to claim 16, wherein a first playoutbuffer feature from the plurality of playout buffer features correspondsto a minimum playout buffer size, wherein the minimum playout buffersize indicates a minimum number of media segments that represents thepre-encoded media assets and/or the live input streams, as defined inthe first programming schedule, wherein a second playout buffer featurefrom the plurality of playout buffer features corresponds to a maximumplayout buffer size, wherein the maximum playout buffer size indicates amaximum number of media segments that represents the pre-encoded mediaassets and/or the live input streams, as defined in the firstprogramming schedule, wherein a third playout buffer feature from theplurality of playout buffer features corresponds to a default playoutbuffer size, wherein the default playout buffer size indicates apre-specified number of media segments that represents the pre-encodedmedia assets and/or the live input streams, as defined in the firstprogramming schedule, wherein a fourth playout buffer feature from theplurality of playout buffer features corresponds to an altered playoutbuffer size, and wherein the altered playout buffer size indicates analtered number of media segments that represents the pre-encoded mediaassets and/or the live input streams, as defined in the firstprogramming schedule.
 18. The method according to claim 17, furthercomprising setting, by the processor, a playout buffer duration for themedia segments in accordance with the second playout buffer feature whena desired playout buffer duration exceeds a maximum playout bufferduration as defined in the first programming schedule.
 19. The methodaccording to claim 17, further comprising determining, by the processor,the fourth playout buffer feature based on a reference to a repositoryof schedules, rights, and preferences database or a third-party databaseby the first programming schedule.
 20. The method according to claim 19,further comprising validating, by the processor, that the media segmentsassociated with the stream identifier are eligible in accordance withthe fourth playout buffer feature enabled via constraints and rights.21. The method according to claim 20, further comprising setting, by theprocessor, a default playout buffer duration for the media segments whenthe media segments associated with the stream identifier are ineligiblein accordance with the fourth playout buffer feature, wherein thedefault playout buffer duration is defined in the first programmingschedule.
 22. The method according to claim 20, wherein, when the mediasegments associated with the stream identifier are eligible inaccordance with the fourth playout buffer feature and the additionalparameter comprises both of a user identifier and an altered playoutbuffer duration flag, the method further comprising: querying, by theprocessor, the repository of schedules, rights, and preferences databasebased on the user identifier; receiving, by the processor, a permissibleplayout buffer duration for the media segments based on the query; andsetting, by the processor, a playout buffer duration for the mediasegments based on the received permissible playout buffer duration. 23.The method according to claim 22, wherein, when the media segmentsassociated with the stream identifier are eligible in accordance withthe fourth playout buffer feature and the additional parameter comprisesa desired playout buffer duration for the media segments associated withthe stream identifier, the method further comprising setting, by theprocessor, a playout buffer duration for the media segments based on thedesired playout buffer duration.
 24. The method according to claim 23,further comprising playing out, by the processor, the generated firstdisparate live media output stream, wherein the first disparate livemedia output stream manifest continues the insertion of the manifestdata and indexed metadata of the media segments until a total number ofthe media segments reaches the desired playout buffer duration.
 25. Themethod according to claim 23, further comprising playing out, by theprocessor, the generated first disparate live media output stream,wherein the first disparate live media output stream manifest maintainsthe playout buffer duration based on removal of the manifest data andindexed metadata of an oldest media segment for each insertion of themanifest data and indexed metadata of a new media segment when thedesired playout buffer duration is reached.
 26. The method according toclaim 16, further comprising: querying, by the processor, an indexingand storage system based on the received request, wherein the querycomprises the stream identifier; and determining, by the processor, thefirst programming schedule, the manifest data and the indexed metadataassociated with the query, wherein the manifest data and the indexedmetadata correspond to the media segments associated with the streamidentifier to be inserted to the first disparate live media outputstream manifest in accordance with the first programming schedule, theplayout buffer feature from the plurality of playout buffer features,and at least the additional parameter.
 27. The method according to claim16, further comprising validating, by the processor, that media segmentsassociated with the stream identifier are eligible for a playout. 28.The method according to claim 27, further comprising generating, by theprocessor, an error notification when the media segments associated withthe stream identifier are ineligible for the playout.
 29. The methodaccording to claim 27, wherein, when the media segments associated withthe stream identifier are eligible for the playout and the additionalparameter does not comprise an altered playout buffer duration flag or adesired playout buffer duration, the method further comprising setting,by the processor, a default playout buffer duration for the mediasegments as defined in the first programming schedule.
 30. Anon-transitory computer-readable medium having stored thereon, computerimplemented instruction that when executed by a processor in a computer,causes the computer to execute operations, the operations comprising:receiving a request that comprises a stream identifier and an additionalparameter; and generating a first disparate live media output streambased on an insertion of manifest data and indexed metadata of a mediasegment associated with the stream identifier to a first disparate livemedia output stream manifest in accordance with a playout buffer featureof a plurality of playout buffer features and the additional parameter,wherein the playout buffer feature, defined in a first programmingschedule, is associated with a corresponding number of media segmentsrepresenting pre-encoded media assets and/or live input streamsreferenced in the first programming schedule.